Scrambles Matcher Mega-Issue

[dunkOnIT]

Functionality

• Give delegates the ability to change scramble_sets from within the matcher page
• When switching events, open the contents of the first round by default (currently none of the rounds are open)
  • Concern was that users might get confused based on whether their intuition is that the first/last round would be opened by default - I'm (Duncan) comfortable that most users will intuitively expect it to be the 1st round
• Scrambles Matcher: Allow organizers to mark the number of scrambles used in MBLD, and mark the others as extra #12868
  Currently, the delegate specifies the number which were used when submitting results, and WRT manually removes them as part of the posting process.

I'm not too privy to the implementation here, but my first thought is to split the MBLD scramble set into a "used" and "unused" set/ truncate the scrambles present in the MBLD set and add the unused ones to a scramble set that gets put in the "extra" section - with the option for the user to change the number of scrambles used in the set

• Extra scrambles show "Extra 6" and "Extra 7" instead of "Extra 1/2" (Gregor says he already knows how to fix this)
• Assign extra scrambles to the "Unmatched Scrambles" section by default

Reported by Christofer Alejandro Aguirre Robledo in email thread "New Results Upload Process: Seeking Testers", where he confirmed that the following is the desired behaviour (feature requirement for this issue bolded):

For 333 Round 1, you select "4" under "Scramble Sets" in the Event Manager (I assume this is what you meant by "number of rounds"?)
In TNoodle, you generate 5 scramble sets (n+1, where n=4)
In the competition, you don't use the extra scramble set
Currently, scrambles matcher automatically places that 5th (extra) scramble set inside the 3x3 -> Round 1 menu, meaning you need to click in and remove it/mark it as unused
Instead you would prefer that the 5th scramble set goes into the "Extra Scrambles" section, where you can assign it if you would like to

• If a subsequent scramble file is uploaded (eg, the delegate had to generate extra scrambles on the fly), all those scrambles should be placed in the "extra scrambles" section, instead of being auto-assigned
• [BLOCKED pending WRC's feedback in "Query on Scramble Cross-Matching"] Allow cross-matching of scrambles generated for the non-target event based on WRC's feedback

As discussed in Slack, we also want the following behaviour:
(1) Illegal scramble matches - this won't be allowed by the UI ideally, but if somehow an illegal match is made, we will raise errors as is normal in the results posting process that revent the delegate for submitting
(2) Allowed cross-matches - we will have a warning visible for both delegates and WRT that non-standard-but-allowed-by-regs scrambles have been used.
(3) Additionally, in the scrambles table, we will retain the id of the event that the scrambles were originally generated for

UI/UX

• Explicit explanatino of what "Auto-Assign"/"Manual" do (question mark that the user can hover over?)
• Remove "Refresh" button next to "Upload from TNoodle" (or check for admin privileges before displaying it, if it is still desireable for debugging in prod, or put it behind a prod check)

[dunkOnIT]

Task progress will be tracked in this spreadsheet. Non-WST members should comment their interest before working on any of these, to prevent redundant work.