Tracking tasks per each new collection

[acwhite211]

Fixes #7779

Implement a better solution on preventing users from logging into new collections that don't have all their celery background tasks completed. The inital 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 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
• Add automated tests
• Add a reverse migration if a migration is present in the PR

Testing instructions

TBD