[Test] Cache arena tag matcher types; fix BattlerTag matcher distributiveness

[Bertie690]

What are the changes the user will see?

N/A

Why am I making these changes?

I noticed toHaveBattlerTag was distributing over B.

This was causing it to show all properties on all battler tags if left unchecked.

What are the changes from a developer perspective?

Made type non distributive

applied similar caching to toHaveArenaTag

Screenshots/Videos

N/A

How to test the changes?

try using the matchers with an empty object:

expect(enemy).toHaveArenaTag({});
//                            ^ ctrl-click here, should only get base class props

Checklist

• I'm using beta as my base branch
• There is no overlap with another PR?
• The PR is self-contained and cannot be split into smaller PRs?
• Have I provided a clear explanation of the changes?
• Have I tested the changes manually?
• Are all unit tests still passing? (pnpm test:silent)