Create co-pilot PR review instructions

[TaylerUva]

All PRs should be reviewed in the context of FRC (FIRST Robotics Competition) robot code. Review current code structure for added context

Enforce our team standards and good FRC practice. For example:

• Our team uses two code subsystems to hold all of our motors FreeSpin.java and Positional.java
• Flag instances of hardcoded numbers that aren't in constants/ folder or DeviceIDs
• We use a state machine

Make generalized instructions (copilot-instructions.md) and Path-specific (*.instructions.md) instructions

• for example the /states folder should have different instructions than the /constants folder

Also use this for conventions:
https://github.com/FRCTeam3255/Wiki/blob/main/Software/Conventions.md

You can also use these code bases as additional structure reference:
https://github.com/FRCTeam3255/2026_CopyBot_Code
https://github.com/FRCTeam3255/2026_Robot_Code