Consolidate individuals' queue table views

[lowellrex]

We have three different ways to display an individual Caseflow user's tasks, one for attorneys, one for judges, and one for everybody else. In addition to increasing the amount of nearly redundant front-end code, this forces the application to care about the current user's role, and complicates the process of extending parts of the application that interact with a user's role (like adding support for acting judges in Caseflow).

Attorney queue	Judge review cases view	Generic (Colocated) queue

This ticket exists as a reference for the more tightly-scoped work tickets that will consolidate those three views into one that can handle all three user roles (while being mostly-agnostic to the user's role on the front-end). Before migrating these three components to a single unified component for each role, we can update the existing components to reduce the impact of the switchover and discover any unexpected snags.

The three queue table views differ as follows:

.	Attorney queue	Judge review cases view	Generic (Colocated) queue
Page title	"Your cases"	"Your cases"	"Review x cases"
Loading error message	Displays error if legacy appeals need DAS assigmment	None	None
Columns displayed	No task type	Has document ID, but no Document count and Reader link	No issue count
Navigation dropdown	Uses standard org dropdown	Uses special QueueJudgeAssignOrReviewDropdown	Uses standard org dropdown
Tabs displayed	Assigned tab view uses workableTasksByAssigneeCssIdSelector, others are the same	Only shows "Assigned" tab view	Assigned tab view uses workableTasksByAssigneeCssIdSelector, others are the same

Acceptance criteria

• Pass columns to display in queue table view from back-end (Pass columns to display in queue table view from back-end #10049)
• Use QueueOrganizationDropdown for judges' queue navigation element (Use QueueOrganizationDropdown for judges' queue navigation element #10048)
• Extend QueueConfig to work for individual (non-org) users Extend QueueConfig to work for individual (non-org) users #11696
• Return QueueConfig to front-end for individual queues Return QueueConfig to front-end for individual queues #11697
• Build generic individual queue from config Build generic individual queue from config #11698
• Build attorney queues from config Build attorney queues from config #11699
• Build judge queues from config Build judge queues from config #11700
• Add tabs to judges' individual queue table views (Add tabs to judges' individual queue table views #10044)
• Use single method for collecting assigned tasks for individual queues (Use single method for collecting assigned tasks for individual queues #10047)
• Use single component for these three scenarios
• Unify individual queue table view titles (Unify individual queue table view titles #10043)

[anyakhvost]

This looks good to me. Thank you putting it together.

[lpciferri]

@jimruggiero FYI, this is really good refactoring and tech debt work for echo to close out as they have time when other priority initiatives are blocked. We currently have 4 types of individual queues (judge, attorney, vlj support, and individual), which is confusing!