[Move] Partially Implement Instruct

[Bertie690]

Locales PR

What are the changes the user will see?

Instruct will actually work and calls the target's last used move correctly.
It currently does not play nice with Gigaton Hammer, Blood Moon and Torment, but those are related to the janky implementation of those moves currently. #4289
Also pledge jank happens currently.
Also the enemy cannot really use it atm but whatevs

Why am I making these changes?

Because I want funny klefki prankster instructing power trick shuckle rock slide.

What are the changes from a developer perspective?

Added RepeatMoveAttr for moves that force targets to repeat moves themselves. (This is distinct from CopyMoveAttr which has the user use a target's previous move)

Screenshots/Videos

Instruct repeating an ally's rock slide & subsequently failing on enemy Unown due to not having made moves yet:

Untitled.video.-.Made.with.Clipchamp.mp4

pp after instruction

It sorta works on pledges... a bit
https://github.com/user-attachments/assets/60490c80-57bd-43cd-8d0b-66ea511803bb
Instruct fails if used on Instruct/Outrage (Full list of moves on Bulbapedia):
https://github.com/user-attachments/assets/b9a22fa2-ab67-4d1d-bd6b-81b855fa545a
https://github.com/user-attachments/assets/59e6ef89-5a7c-477e-a2d0-469ce402b5c7

How to test the changes?

Run npm run test instruct

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?

[innerthunder]

Get rid of all the changes to overrides, package-lock.json, and package.json.

[Bertie690]

Requesting #3503 to be updated with this PR thz

(Also feedback on tests is welcome - half of them are failing and IDK why)

[innerthunder]

Btw, please don't use your fork's beta branch for PRs. It makes it hard for us to checkout your branch for playtesting without affecting our own beta branch.

The best practice for dev work is to make a new branch for every PR/feature, named differently from any of the existing branches on upstream.

[Bertie690]

Btw, please don't use your fork's beta branch for PRs. It makes it hard for us to checkout your branch for playtesting without affecting our own beta branch.

The best practice for dev work is to make a new branch for every PR/feature, named differently from any of the existing branches on upstream.

I completely forgot about this when making the branch.
In that case I'll close this PR and make a new one.
Thx for letting me know.

[Bertie690]

Closing PR to change commit branch.