[Bug] Fix some trapping moves' interactions with Ghost-type Pokemon

[innerthunder]

What are the changes the user will see?

This fixes two issues related to how certain trapping moves interact with Ghost-type Pokemon:

1. If a Ghost-type Pokemon is hit with a binding move (e.g. Infestation), it is now correctly afflicted with the damaging effect (while still able to switch or run), rather than cancelling the move's secondary effects altogether.
2. Ghost-type Pokemon are no longer able to use No Retreat multiple times in succession.

Why am I making these changes?

closes #1915

What are the changes from a developer perspective?

• data/battler-tags: New NoRetreatTag that extends TrappedTag but removes the non-Ghost-type condition for adding. This condition is also removed from DamagingTrapTag, as this condition can instead be found in Pokemon#isTrapped
• data/move: Changed No Retreat to make use of its new tag type.
• field/pokemon: Added an isTrapped helper function to Pokemon which returns true when the Pokemon is under the effects of a trapping move or ability. This supports simulated calls to Shadow Tag, etc. and can forward ability trigger messages to UI elements via the trappedAbMessages argument.
• phases/command-phase and phases/enemy-command-phase: Rewrote checks for trapping using Pokemon#isTrapped

Screenshots/Videos

Showing Infestation's effects on a Ghost-type vs. on a non-Ghost-type:

PokeRogue.-.Google.Chrome.2024-08-31.00-54-05.mp4

Showing No Retreat fails after the first use by a Ghost-type (but the Ghost-type can still switch):

PokeRogue.-.Google.Chrome.2024-08-31.00-54-47.mp4

How to test the changes?

To reproduce the video tests, add the following overrides to src/overrides.ts:

const overrides = {
  STARTER_SPECIES_OVERRIDE: Species.GENGAR,
  MOVESET_OVERRIDE: [Moves.SPLASH, Moves.NO_RETREAT],
  OPP_MOVESET_OVERRIDE: Array(4).fill(Moves.INFESTATION)
} satisfies Partial<InstanceType<typeof DefaultOverrides>>;

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?
• 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?