Don't block execution when waiting for startup tasks

[JosephMarinier]

Description:

• Avoid checking .done() twice
• Check for startup status a lot more frequently and log status updates only when there are some changes (to avoid spamming the user with logs).
• Log progress in a separate thread
• Always log statuses in the same (logical) order and in one multiline log to make sure no logs from other processes get inserted in between.

Checklist:

You should check all boxes before the PR is ready. If a box does not apply, check it to acknowledge it.

• ISSUE NUMBER. You linked the issue number (Ex: Resolve #XXX).
• PRE-COMMIT. You ran pre-commit on all commits, or else, you
  ran pre-commit run --all-files at the end.
• USER CHANGES. The changes are added to CHANGELOG.md and the documentation, if they impact
  our users.
• DEV CHANGES.
  • Update the documentation if this PR changes how to develop/launch on the app.
  • Update the README files and our wiki for any big design decisions, if relevant.
  • Add unit tests, docstrings, typing and comments for complex sections.

[gabegma]

I really like the idea!! However, when I tried, I felt more spammed with logs than before; it prints so quickly that it can be hard to follow, as blocks of logs follow each other and it can be hard to see where it starts and ends. I tried a sleep of 5 seconds, and I think it is easier to follow what is going on. What do you think?

[gabegma]

I love this - this is great!!! The logs are prettier too. Thanks a lot for tackling this! I learned about threading a bit more.

[JosephMarinier]

Cool! Thank you! I learned it too!