Build judge queues from config

[lowellrex]

In order to complete the move to defining judge queues on the back-end we should use the same front-end arrangement that we used to satisfy the similar ticket for generic individual queues (#11698). This may not be as straightforward as generic queues since a fair amount of front-end Queue code relies on the user's role and we may need to untangle that code in order to complete this ticket.

🚫 Blocked by

• Build generic individual queue from config Build generic individual queue from config #11698

Acceptance criteria

• Use same component for judge queues that we used for generic individual queues in Build generic individual queue from config #11698

[lowellrex]

What is this graph?

      1 | 
      2 | ||||
      3 | ||||||
      5 | ||
      8 | 

#11698 blocks this because one of this series of tickets has to come first and that one looks like the simplest case.

Judge queues are different than attorney and generic task table views because they don't have tabs and they do have dropdown menus.

Estimating at 3. Possible 2 because the appearance of a single tab might already be handled on the front-end so the major complication would be the dropdown for judges and that might be easy enough to attack. Possible 5 because differences between different queues might actually not be that similar and unwrapping the drift between files that should be similar might be a nightmare.