Breaking: Rule Tester strictly checks messageId and data. (fixes #9890)

[betaorbust]

What is the purpose of this pull request? (put an "X" next to item)

[ ] Documentation update
[x ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[x] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

This PR:

1. Addresses the solution discussed in the comments on messageId messages with placeholders fail during tests. #9890
2. Adds associated tests.
3. Adds message formatting data to the reported problem object. (Related to 1, but also very useful for deeper checking, and future localization work based off of messageId
4. Fixes some unrelated tests that were either throwing whole nodes into the data field, just to pull off name or were relying on a hard-coded problem object shape.

Is there anything you'd like reviewers to focus on?

• This is technically a breaking change, as there are some stricter assertions around message, messageId, and data usage in rule-tester.
• Unfortunately, the data property is somewhat generically named, but I left it that way to keep parity with what's actually being set during context.report. Any suggestions on that would be helpful, but I think this is probably the right name, if unfortunately a little ambiguous.

[platinumazure]

Hi @betaorbust, should this be closed? Thanks!

[betaorbust]

Closing in favor of #9908