Add easy match number selection field

[andrewda]

Right now scouts are match agnostic. Make a new field to allow for the selection of a match, or entering the match number. This should also be the name of the scout instead of relying on the human to name the scout, which rarely gets done.

One option could be just having a dropdown with "Q", "QF", "SF", "F" with a text box next to it for the match number, followed by a conditional second text box if we're in "QF" or "SF" for the series number.

Another option could be getting match schedules from TBA and having a searchable dropdown of all the matches.

The latter will be needed for #55, so might be a good idea to spend the time on it anyways, but having the former as a backup in case there isn't any match schedule (or one couldn't be downloaded before we lost internet access) would be a good idea too.

[andrewda]

Also, if more linking to events gets done, naming the scouts something like {eventId}_{matchId} would be really good too so we can easily link it to the TBA match using the same format.

[andrewda]

When selecting the match from a dropdown, only the matches in which that team plays should be shown.

[SUPERCILEX]

Yup, already planned for #55. The scout names will be XXX-### where XXX = QF. I'm not going to provide any UI for this since Auto Scout will automatically create a new scout for you and bring you to the right Activity from the notification.

[andrewda]

There should be UI to change it in case anything is wrong. Manual override but default it to what you think it is. And for the number follow TBA's naming: qm54, qf2m2, sf1m2, and f1m1.

[SUPERCILEX]

Nah to both. The match names needs to be human readble and the override won't be there. You'll be able to say the match number you're currently playing and you'll tell it when to move on to QF or F etc. Foolproof that way.

[andrewda]

Hmm okay, that's kinda what I was talking about wrt the "override". Also, I'm good with a human readable format ("Qualification 54", "Quarterfinal 2 Match 2", "Semifinal 1 Match 2" and "Final 1 Match 1"), but when exporting it it'd be super nice to have the match code so it can be easily linked to the TBA match without having to parse it in a gross way.

[SUPERCILEX]

Yeah, that'll only be for the JSON though. I've added that to the list, good idea. 👍