Rewrite internal architecture to be more flexible

The internal scheduling architecture was rewritten:

Instead of using one task per dispatch that will start/stop them,
we now have a queue of events and a timer that is rescheduled
to the earliest next event each time it triggers.

Previously we had to do complicated re-scheduling and cancelling of
tasks, now we always just update the event in the queue.

Signed-off-by: Mathias L. Baumann <[email protected]>

Author: Marenz

pyproject.toml

@@ -40,9 +40,10 @@ dependencies = [
   # mkdocs.yml file when changing the version here (look for the config key
   # plugins.mkdocstrings.handlers.python.import)
   "frequenz-sdk == 1.0.0-rc900",
-  "frequenz-channels >= 1.1.0, < 2.0.0",
+#  "frequenz-channels >= 1.1.0, < 2.0.0",
+  "frequenz-channels @ git+https://github.com/frequenz-floss/frequenz-channels-python.git@refs/pull/323/head",
 #  "frequenz-client-dispatch >= 0.6.0, < 0.7.0",
-  "frequenz-client-dispatch @ git+https://github.com/frequenz-floss/frequenz-client-dispatch-python.git@v0.x.x",
+  "frequenz-client-dispatch @ git+https://github.com/frequenz-floss/frequenz-client-dispatch-python.git@refs/pull/87/head",
 ]
 dynamic = ["version"]