feat!: capitalize default pattern of require-meta-docs-description rule

[azat-io]

This PR modifies the default pattern value of ESLint rules description.

Currently almost all ESLint plugins use descriptions starting with a capital letter.

ESLint rules, example:
https://github.com/eslint/eslint/blob/main/lib/rules/accessor-pairs.js#L149

TypeScript ESLint rules, example:
https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/src/rules/adjacent-overload-signatures.ts#L29

ESLint React:
https://github.com/jsx-eslint/eslint-plugin-react/blob/master/lib/rules/boolean-prop-naming.js#L47

ESLint Import:
https://github.com/un-ts/eslint-plugin-import-x/blob/master/src/rules/consistent-type-specifier-style.ts#L57

ESLint Promise:
https://github.com/eslint-community/eslint-plugin-promise/blob/main/rules/always-return.js#L162

ESLint Unicorn:
https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/rules/better-regex.js#L138

ESLint Perfectionist:
https://github.com/azat-io/eslint-plugin-perfectionist/blob/main/rules/sort-array-includes.ts#L104

I think we should change the default behavior of the rule, since even ESLint itself doesn't adhere to it and writes descriptions for rules with a capital letter.

[aladdin-add]

👍 I support it. However this is a breaking change, we'll have to wait until the next major release to consider it. / @bmish

[bmish]

If most of the top plugins use sentence case, then I'd be open to this.

For context, I found the PR where ESLint switched over to sentence case descriptions:

• docs: Remove duplicate rule descriptions eslint/eslint#16052

[Zamiell]

I support this PR! (Today, I had to make this change manually and was surprised that it was not the default.)

[azat-io]

Rebased