feat(syncwaves): use binary tree ordering for sync waves

[SebastienFelix]

No description provided.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 48.63%. Comparing base (8849c3f) to head (cf27063).
Report is 52 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #744      +/-   ##
==========================================
- Coverage   54.26%   48.63%   -5.64%     
==========================================
  Files          64       64              
  Lines        6164     6718     +554     
==========================================
- Hits         3345     3267      -78     
- Misses       2549     3194     +645     
+ Partials      270      257      -13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
15.8% Duplication on New Code

See analysis details on SonarQube Cloud

[alexec]

Is this trying to address the same issue as #514 ?

[SebastienFelix]

@alexec : kind of, I guess!
The main goal of this feature is to avoid wasting time by waiting for non-related resources to be synced before proceeding a given resource.

I thought about defining the dependencies relation graph the way you did it but I thought that managing the circular dependencies would be too complicated.

The way I did it in this PR completely avoid this issue and avoids adding more complexity with another logical layer.

I openned an issue for that here #734

My solution would allow the implementation of the feature described here #3517 by syncing the applications in parallel and avoiding a stuck component of one application blocking all the resources having a greater syncwave value.

As an example from the mentionned issue :
If the infra-prometheus-operator get stuck during deployment, it would only block the deployment of infra-prometheus-alertRules/grafanaDashboard/thanos

Here is the syncwaves values and the induced dependencies related to the issue #3517

WDYT?

P.S : after creating this graph, I realize than the syncwave values would be much more human-readable using base 10 instead of base 2 in my graph. Then the graph would look like that :