Code Quality Tools for 3.2.0 and beyond

The next [release 3.1.0](https://github.com/meteor/blaze/pull/492) has gained momentum and it already contains lots of changes.

At the same time I found, that there is no linter / formatter integrated. This is mostly, because lots of the code wasn't even ready to be linted until recently (for example, see #488).

Finally, there is a [discussion in the community about code standardization for the Meteor Core](https://forums.meteor.com/t/meteor-codebase-standardization/64495/13). I think this is the right time for us to discuss, which code quality tool we want to use.

While I personally prefer biome for its opinionated out-of-the-box style, I also like the idea to be par with the Meteor Core codebase tools (which seems to be OXC).

## Next steps

While release 3.1.0 is still in the works, we should use the momentum and decide for a code quality tool, which will be integrated into the codebase for our [next release 3.2.0](https://github.com/meteor/blaze/milestone/12), for which development will start right after 3.1.0 has the first alpha release out.

Again, while I personally prefer Biome, I think we should go with the decision for Meteor Core.

Start by reviewing the release 3.1.0 pull request (#492), the code-readiness issue (#488), and the linked Meteor Core standardization discussion. Compare the proposed code-quality tools and document the project decision, then define what integration for the 3.2.0 milestone would require; no files or tests are named in the issue.

Written by the indexing model from the issue text.