breaking: add recommended rules prefer-message-ids, prefer-output-null, no-missing-message-ids, no-unused-message-ids

[bmish]

Enable additional recommended rules:

• prefer-message-ids: message IDs have become best practice, ESLint core enforces this rule already
• prefer-output-null: this will enforce upcoming ESLint v9 behavior from an approved RFC
• Add new rules no-missing-message-ids and no-unused-message-ids #254

Remove from recommended:

• consistent-output: no longer necessary since ESLint v7 validates that test cases provide output when they produce an autofix, and it's tedious to include output: null when not necessary, so we shouldn't require it

Part of v5 release (#230).

[aladdin-add]

consistent-output: no longer necessary since ESLint v7 validates that test cases provide output when they produce an autofix, and it's tedious to include output: null when not necessary, so we shouldn't require it.

it's no harm not to remove it - linting can find the error earilier(IDE)?

[bmish]

@aladdin-add I'm definitely in favor of rules that can catch issues early even when ESLint itself would also catch the issues.

consistent-output can be helpful in this regard, but "consistency" is an imperfect heuristic. Just because some test cases for a rule have an autofix doesn't mean that all the rule's test cases do, which is why I think it can sometimes be tedious how this rule requires specifying output: null for the non-fixable test cases even though that's already the implicit behavior.

That said, I've removed the change to this rule from this PR since many people will still find the rule helpful and it's less churn to leave as-is now.