feat: support aliases for jest globals (e.g. context)

[G-Rath]

I'm a bit on the fence about this: it ended up being a pretty straightforward addition but I'm worried it's catering to a very small niche because:

1. it requires you to set up the globaled aliases with a custom setupTestFrameworkScriptFile
2. you can get this already by importing the function you want to alias from @jest/globals
   • in addition to being a requirement if you're using ESM (since no globals), I think it's straight up easier than 1 as devs will already know how to import but would need to readup on jest configuration to know how to do 1

@SimenB do you think this is worth landing?

Resolves #83

[G-Rath]

hmmm having this could allow us to deprecate the additionalTestBlockFunctions option that we've got on a few tests, which should reduce the logic of our rules and maybe improve some other rules for people (e.g. #534) without us having to do anything; so that could be another reason to land it.

[SimenB]

I think this seems reasonable 👍

[G-Rath]

@SimenB do you think it's worth us checking if we can remove some of our rule options in favor of this?

[github-actions]

🎉 This PR is included in version 26.5.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[G-Rath]

double hmmm: actually if we made this support checking local declarations (just for aliases - jest native functions would still be expected to be either globals or imported from @jest/globals), I think it should allow all of our rules to be customisable when combined with overrides.

This'd definitely let us drop a few rule-specific options, and resolve e.g. #1033