[Misc][Move] Add waveTurnCount to PokemonBattleData

[DayKev]

What are the changes the user will see?

Fake Out and First Impression (and Mat Block) can be used at the start of every wave again.

Why am I making these changes?

Slight buff for a couple of moves (requested by @damocleas), and new field in PokemonBattleData that can be used for other things later.

What are the changes from a developer perspective?

waveTurnCount: number = 1 added as a field to PokemonBattleData.
FirstMoveCondition updated to use the new field, allowing moves like Fake Out to be used at the start of every wave even if the Pokémon has been out for multiple turns.

How to test the changes?

npm run test fake_out

Checklist

• I'm using beta as my base branch
• There is no overlap with another PR?
  • Modified version of [Hotfix] Allow Fake Out to be used at the start of every wave again #4105
• The PR is self-contained and cannot be split into smaller PRs?
• Have I provided a clear explanation of the changes?
• Have I considered writing automated tests for the issue?
• [ ] If I have text, did I make it translatable and add a key in the English locale file(s)?
• Have I tested the changes (manually)?
  • Are all unit tests still passing? (npm run test)
• [ ] Are the changes visual?
  • [ ] Have I provided screenshots/videos of the changes?

[Tempo-anon]

To be honest, not a huge fan with a specific hardcoded case just for certain moves and not others. Things should be consistent and not just have kneejerk changes based on vibes, and it seems a lot of complaining about fake out has died off now too.

[damocleas]

To be honest, not a huge fan with a specific hardcoded case just for certain moves and not others. Things should be consistent and not just have kneejerk changes based on vibes, and it seems a lot of complaining about fake out has died off now too.

you do not see all the feedback I do, there are still consistent complaints and it will feel even worse when we have a real doubles mode