feat(no-desc): inadequate-description rule

[gregswindle]

User story

As an API producer and consumer,
I must provide a succinct and expressive API object, method, and property descriptions
In order to express the API's value and usage to (potential) consumers.

Acceptance criteria

• 1. required {boolean} Declares whether a description must be written.
• 2. minChars {number} A minimum character count can be configured.
• 3. maxChars {number} A maximum character count can be imposed.
• 4. markdown {boolean} Require markdown formatting in the description (or not).

⚡ Rule developers must use the eslint:rule subgenerator!

When you create a new rule, be sure to use the eslint:rule subgenerator, since it will

1. Create a stubbed rule,
2. The rule's stubbed BDD specs,
3. As well as the rule's documentation.

See eslint-plugin development environment for details.