Unblock login after new discipline from config tool creation

[acwhite211]

Fixes #7774

Prevent a new discipline being created in the background from the user being able to login to a collection from an already existing discipline. Also, this solution needs to preserve the functionality of preventing the user from logging into a new collection before it is fully completed.

It seems this issue of new disciplines is being caused as a side-effect of the solution to preventing new collections from being used before they were fully ready.

While a new discipline was being created, background config Celery tasks were treated as global “setup in progress.” That made the login page show Guided Setup for users and could block login/collection switching even for unaffected collections.

The setup_progress busy variable now reflects only true initial database setup, not generic config tasks. Config-task blocking is collection aware, so only newly created collections are blocked, and existing collections and disciplines remain available.

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

Checking login after created a new discipline:

• Open the configuration tool page.
• In a separate private browser window, open up the login page, type in the login username and password, but don't login yet.
• In the configuration tool, go through the process of creating a new discipline. Make sure to configure a new tree to be uploaded for the new discipline. Before finsihing the discipline creation, be ready to quickly switch to the login page.
• As soon as you press "Save" for the new discipline in the login page, quickly switch to the login page in your separate private window login any of the existing collections.
• See that you can login while the discipline and it's tree are still being created.

Checking login after creating a new collection:

• In the private browser window, logout, and set it up so you can quickly log back in later.
• In the other browser window, use the configuration tool to create a new collection.
• After pressing "Save" to create the new collection, quickly switch over to the private browser window to try logging in.
• Confirm that the new collection is not yet available as an option of login as.
• Want sometime for all the background processes to end for creating the new collection, and the try logging in to the new collection.

[alesan99]

• See that you can login while the discipline and it's tree are still being created.
• Want sometime for all the background processes to end for creating the new collection, and the try logging in to the new collection.

---

Looks good! 👍

Logins work correctly and new collections appear after a while. I wasn't able to trigger the database setup loading page through the config tool, so that works.

[alesan99]

@acwhite211 After trying the current behavior on main, I noticed that this PR doesn't wait for tree creation to finish before letting you log into the database during the initial database setup.
Should this be changed? I think there would some issues with the reliability of the tree loading messages before, which should be fixed now I think, so this might be okay. But it may be a problem for other background tasks.

[CarolineDenis]

@acwhite211, yes this needs to be changed

[bhumikaguptaa]

Checking login after created a new discipline:

• See that you can login while the discipline and it's tree are still being created.

Checking login after creating a new collection:

• Confirm that the new collection is not yet available as an option of login as.
• Want sometime for all the background processes to end for creating the new collection, and the try logging in to the new collection.

Everything works as expected, I didn't run into any errors. I was able to view the new collection without logging out and back in.