[Bug/Refactor] Block moves that shouldn't be selectable under certain conditions, refactor Gravity

[schmidtc1]

What are the changes?

Some moves shouldn't be selectable in the move menu under certain conditions.
Refactors Gravity and the Interrupted tag.

• Gravity prevents 'flying' moves
• Stuff Cheeks cannot be used without a berry

Why am I doing these changes?

It is the correct implementation of the moves.

What did change?

Adds UnselectableMoveAttr to the following moves:

• Stuff Cheeks
• Bounce
• Fly
• Flying Press
• High Jump Kick
• Jump Kick
• Magnet Rise
• Sky Drop
• Splash
• Telekinesis

Adds a check in isUsable() for determining if a move can be selected.
Adds a check in MovePhase for displaying the failed text specific to these moves.
Removes the lapse() function from InterruptedTag. All functionality moved to onAdd() and tag is removed immediately after.
(NOTE: debating whether Interrupted tag should just be removed and place functionality in move.ts as an attribute of Gravity, Smack Down, and Thousand Arrows.)

Screenshots/Videos

Stuff cheeks

Stuff.cheeks.blocked.mp4

Gravity moves

Gravity.moves.mp4

Struggle when no moves are usable

Struggle.with.no.usable.moves.mp4

Semi-invulnerable airborne moves cancelled before second turn goes off

Fly.cancelled.mp4

To-do

• Update messages to match canon game.
• Put in text for when Fly/Two turn move is cancelled by gravity (while user is in air).
  • Check if it works in onAdd()/if it affects anything else.
• Write unit tests.
  • Check if Gravity Arena Tag lasts for 5 turns
  • Check if Gravity interrupts Fly
  • Check if Gravity causes jumping/airborne moves to fail
  • Check if Gravity allows Flying types to be hit by Ground type moves (Merged from [Bug] Fix: Gravity tag removes flying type during damage calculation #3670)
  • Check if Gravity allows Levitate pokemon to be hit by Ground type moves
  • Check if Gravity removes Magnet Rise and allows pokemon to be hit by Ground type moves
  • Check Stuff Cheeks fails if berry is lost before move goes off.

How to test the changes?

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 considered writing automated tests for the issue?
• 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?

[DayKev]

Seems like there might be overlap with #2051 in functionality?

[schmidtc1]

Seems like there might be overlap with #2051 in functionality?

Wasn't aware of that PR, looks like a decent amount of overlap