[Bug] Fix Assist bug of using only the user's moveset instead of whole team's, refactor Assist/Sleep Talk/Metronome implementation

[schmidtc1]

What are the changes?

Properly implements Assist.
Refactors RandomMovesetMoveAttr to extend RandomMoveAttr.
Creates arrays of invalid moves for each move: Assist, Sleep Talk, Metronome, since they each have different sets of uncallable moves.

Why am I doing these changes?

Assist did not call ally moves, had useless code, and was given no distinction in logic from Sleep Talk.
Metronome calls random moves in a similar manner to the two other moves, so it makes sense to have Assist/Sleep Talk reuse the code for calling moves.
None of Assist/Sleep Talk/Metronome had properly implemented lists of uncallable moves.

What did change?

• Assist now uses the entire team's party
• Assist/Sleep Talk's attribute now extends RandomMoveAttr and uses its callMoves function (which has been modified slightly to accommodate this) to call the move
• Sleep Talk targeting is changed to NEAR_ENEMY
• Assist/Sleep Talk/Metronome now have individual arrays listing uncallable moves. These arrays were created referencing Bulbapedia's list of uncallable moves.
• Uncallable moves for Assist
• Uncallable moves for Sleep Talk
• Uncallable moves for Metronome

Note: Sleep Talk specifies that it targets the opposite opponent. Since there is no MoveTarget specifically for opposite opponents, I chose to make it NEAR_ENEMY for now.

Screenshots/Videos

Metronome

Metronome.mp4

Assist

Assist.mp4

Sleep Talk

Sleep.Talk.mp4

How to test the changes?

Checklist

• 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? (npm run test)
• Are the changes visual?
  • Have I provided screenshots/videos of the changes?

[schmidtc1]

Misclicked the close with comment button

[DayKev]

I would like feedback on the following:

• If the IGNORE_VIRTUAL flag can be removed since it is only used for Assist/Sleep Talk/Metronome

Oh, the only things in the codebase that use IGNORE_VIRTUAL are these moves? Removing it is probably fine then, I'm not entirely sure what it was supposed to do (since it seems like it's trying to do multiple things at once but not actually doing any of them correctly lmao).

As for using the same MoveAttr for multiple moves here, do whatever makes it easier to read and maintain. If reusing the same attr for all of them makes the code better, do that; if it makes the code start becoming overly complex/convoluted, then go ahead and separate the attrs.