Tracking tasks per each new collection

[acwhite211]

Fixes #7779

Implement a better solution for preventing users from logging into new collections that don't have all their celery background tasks completed. The initial solution we had was to check if any background tasks were running, and if so, don't allow new collections being used that were less than 15 minutes old to be safe. This new solution uses redis to match and track specific collection IDs to specific background tasks running on celery, so that we can verify exactly if a specific new collection has all of it's associated tasks completed, and thus can be safely used by the user.

Checklist

• Self-review the PR after opening it to make sure the changes look good and
  self-explanatory (or properly documented)
• Add relevant issue to release milestone
• Add pr to documentation list

Testing instructions

Setup Tool

• Create a new database with the setup tool and make sure to create a large default tree.
• For dev testers, check the logs from the worker container to make sure no tree creation task is still running when the UI changes from the database loading page to the login page.

Config Tool Create Discipline/Collection

• Open the configuration tool page.
• Create a new discipline, preferably with a large tree.
• Quickly after creating the discipline, create two or three collections within that discipline.
• Refresh that page every minute or so (probably only every few on the test panel) and use 'Change Collection' in the sidebar to check if you are able switch to any of the new collections yet.
• If refreshed frequently enough, you might see each collection added to the available login options individually as they each finish their own background tasks. If the collections finished quickly, you should at least see all the new collections as options to login as.
• Create one more collection the config tool and then immediately refresh the page.
• When the page is refreshed, click "Change Collections", you should still see the recently finished collections, but not the one that was just created.
• One last time, create a new discipline, and then quickly perform the final step.
• Finally, try switching between the collections. See that there are no error messages, and no error message saying "discipline creation in progress"

[grantfitzsimmons]

• For dev testers, check the logs from the worker container to make sure no tree creation task is still running when the UI changes from the database loading page to the login page.

• Open the configuration tool page.

• Create a new discipline, preferably with a large tree.

I think we should consider telling the user once they start the creation of a discipline that it may take some time to finish after they click Save. Right now, it just drops them back to the form and they can't log in to any collections below. Not necessarily part of this PR.

• If refreshed frequently enough, you might see each collection added to the available login options individually as they each finish their own background tasks. If the collections finished quickly, you should at least see all the new collections as options to login as.
• When the page is refreshed, click "Change Collections", you should still see the recently finished collections, but not the one that was just created.
• Finally, try switching between the collections. See that there are no error messages, and no error message saying "discipline creation in progress"