Do not pull all user tasks after creating or updating a task

[hschallhorn]

Some work around speeding up user queues was done in #14142 by paginating the initial loading of user tasks. This keeps us from calling QueueForRole, which pulls and serializes every task assigned to, completed by, and sometimes assigned by a user. We call QueueForRole after creating and updating a task as well, resulting in the whole user's queue returned to the front end when only a few tasks were updated or created.

AC

• When creating a task, only return the created and updated tasks to the front end (any parents that have changed status or children that were created)
• After creating a task, the front end reflects all created and updated tasks (tasks with changed status are moved to the correct queue tab without refresh, etc)
• When updating a task, only return updated tasks to the front end (any parents that have changed status or children that were created)
• After updating a task, the front end reflects all updated tasks (tasks with changed status are moved to the correct queue tab without refresh, etc)

[lomky]

what is this chart?

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

Judge Assign page can be used as an exemplar.
Definitely break up into multiple PRs.

Why 3?

• sounds like we may need to write a new call?

Why 5?

• A lot of task actions and tests to revise
• Tracking down all places where tasks are created and changed to make sure the resulting state is correct after receiving tasks back will be a lengthy process