Allows require-description to be turned off for specific rules

[mcongrove]

Adds a new option to require-description, called disableForRules, which allows you to pass an array of rules that require-description will not apply to.

Example usage:

"@eslint-community/eslint-comments/require-description": [
	"error",
	{ disableForRules: ["no-unused-vars"] },
],

This can be especially helpful for overrides which are self-evident amongst users of the codebase.

Requested by #134.

[mcongrove]

@ota-meshi @MichaelDeBoey

Hate to ping y'all, but I'm not sure if you were notified this PR was here because I can't request a reviewer.

[brettz9]

While there were two thumbs-down, it looks like a potentially useful change to me, and one which fits in with the ESLint approach of allowing projects choice.

However, it looks like it will need to be rebased first unless the consensus of the team is against this.

Support might also be added for the case where there are multiple rules, e.g., /* eslint-disable no-unsed-var, no-undef */.