Use the same processes to generate documentation as TSLint core

[JoshuaKGoldberg]

Following #573, it's a bit annoying manually crafting a README.md table. If TSLint itself makes the processes it uses to build docs extensible such that we could use it, that'd make it much easier for general community folks to have custom rulesets with good documentation.

As part of this, we should move the detailed explanations from the wiki into rule metadata and samples.

[JoshuaKGoldberg]

Huh, Codelyzer does this: http://codelyzer.com/rules/

...and has a snazzy playground. Nice.

[JoshuaKGoldberg]

💀 It's time! 💀

TSLint is being deprecated; therefore, it and tslint-microsoft-contrib are no longer accepting pull requests for major new changes or features. See palantir/tslint#4534. 😱

If you'd like to see this change implemented, you have two choices:

• Recommended: Check if this is available in ESLint + typescript-eslint ✅
• Not Recommended: Fork TSLint or tslint-microsoft-contrib locally 🤷‍♂️

👋 It was a pleasure open sourcing with you!

If you believe this message was posted here in error, please comment so we can re-open the issue!