[Refactor] Added BattlerTagLapseType.AFTER_HIT

[ElizaAlex]

What are the changes the user will see?

No changes user-side

Why am I making these changes?

Beak Blast and Shell Trap both implement BattlerTags that have some form of effect when the tag holder is hit but currently, each such effect needs to be handled and checked for individually. Adding a new LapseType to handle these similar tags all at once should help reduce duplicate code, standardize their implementations, and streamline future development.

What are the changes from a developer perspective?

• BattlerTagLapseType.AFTER_HIT has been added
• The implementations of Beak Blast and Shell Trap have been slightly adjusted to use this lapse type
• Instead of handling each tag individually, MoveEffectPhase now lapses all AFTER_HIT tags using lapseTags()
• Minor utility functions have been added in pokemon.ts and battler-tags.ts

How to test the changes?

There should be no change in gameplay, so just proceed as you normally would and watch for any unexpected bugs.
There are also existing tests for Beak Blast and Shell Trap:
npm run test beak_blast
npm run test shell_trap

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)

[torranx]

Overlaps with #2559

[DayKev]

Some minor style consistency nits.

[DayKev]

Are you still around to update this PR? #2559 added a HIT lapse type, but didn't update the existing moves to use it.

[DayKev]

After comparing to the HIT tag type added in 2559, this seems like an AFTER_HIT tag in regards to timing unlike the former which is more ON_HIT, so I renamed the tag from ON_GET_HIT to AFTER_HIT.

[torranx]

this could potentially open up a fix for #4552