Retrieve Decklists via NRDB Auth for Open List Cuts

[Orbital-Tangent]

This may require that profiles for players be implemented in some fashion, via NRDB Auth like ABR. Perhaps this could even be linked to a person's ABR profile somehow.

Two things would need to be implemented in the tournament setup: 1) a setting for "Decklists Required? Y/N" and 2) a setting for "Open Lists in Cut? Y/N"

With both active, during registration someone could link their list from their NRDB profile. This list, or a link to it, would be stored and accessible by a NRDB authed opponent when the two are paired during the Cut.

TOs would need admin access to lists at all times for deck checks, and having tools to dynamically open up or close list sharing during Cut rounds would also be desirable.

[Orbital-Tangent]

In addition to submitting decklists, having them properly formatted for printout would be aces. We'd need the person's name, handle, Corp ID/Deck, and Runner ID/Deck. Basically, we should tailor e-submit of a list to have all the same questions answered as a paper copy (Name/Pronouns/Event/Handle/Decks/Stream Consent/Etc).

[haradan]

This is really a lot of different features, with integrations between several systems. I've split out a bunch of issues.

1. NetrunnerDB-based deck registration UI #114 (player chooses from their private decks at registration)
2. Submit NetrunnerDB deck registration and store for later display #116 (should be suitable for display in all UIs)
3. Display cards from NetrunnerDB deck in registration UI #115 (so they can see what the TO will see)
4. Display registered decks in Tournament Organiser view #117
5. Open list cuts where registered decks are displayed to the players playing each other, with option for TO to turn it on or off (we can probably keep this issue for that)
6. Link to NetrunnerDB in export to AlwaysBeRunning.net #118
7. Possibly some alternative for deck registration by the TO (hopefully we can avoid this)

[haradan]

This should be finished now, though I've raised a few more issues for potential improvements. I'm closing this and we can pick up on separate issues if necessary.