Fix startup dependencies

[gabegma]

Description:

As I was debugging, I noticed a few problems related to dependencies.

• First if dependencies is not None would usually not work since dependencies is often an empty list. It would secede() and rejoin() potentially for nothing.
• The dependencies were working a bit by magic, because if I would be in debug mode and go through the startup task row per row (slowly), some modules would start without waiting for their dependencies. Somewhat it wasn't causing an issue when running at normal speed, but it's safer to define the tasks in start_up_tasks so that any dependencies are already defined in the list. I added a TODO so we can improve this in the future.
• If a startup name was a substring of another startup name, the module would wrongly identify its dependencies. I also added a TODO.
• I increased the occurrence at which we check that the startup is done, so we don't wait longer than necessary. This should also improve some tests speed, and it improves the startup time by 20 seconds on average.

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.