v0.201.0: Got rid of FlowTimeWheelService, and it's integration via O…

…utbox

* recording `FlowEventScheduledForActivation` event (previously, placement moment into the time wheel)
* maintaining `schedule_for_activation_at time` field in denormalized flows Postgres/SQLite tables
* using` schedule_for_activation_at` for queries of flows to process within the main flow executor loop
* in-memory implementation replaced with mirrored lookup tables between FlowID and schedule_for_activation_at time.
* extra unit tests for new operations in flow events store.

CHANGELOG.md

@@ -9,7 +9,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 <!--- - Changed -->
 <!--- - Fixed -->
 
-## [Unreleased]
+## [0.201.0] - 2024-09-18
 ### Added
 - REST API: New `/verify` endpoint allows verification of query commitment as per [documentation](https://docs.kamu.dev/node/commitments/#dispute-resolution) (#831)
 ### Changed
@@ -19,6 +19,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
     - consumption jobs invoke consumers and detect their failures
 - Detecting concurrent modifications in flow and task event stores
 - Improved and cleaned handling of flow abortions at different stages of processing
+- Revised implementation of flow scheduling to avoid in-memory time wheel:
+    - recording `FlowEventScheduledForActivation` event (previously, placement moment into the time wheel)
+    - replaced binary heap based time wheel operations with event store queries
+    - Postgres/SQlite event stores additionally track activation time for the waiting flows
+    - in-memory event store keeps prepared map-based lookup structures for activation time
 
 ## [0.200.0] - 2024-09-13
 ### Added