Fixes #26404: Properties cache is not updated when saving group or global parameters with changed properties

[clarktsiory]

https://issues.rudder.io/issues/26404

We reorganize the hierarchy of calls that update the properties service :

• in groups repo : when groups properties change, right after it is changed in LDAP
• in global parameters repo : after any change in global parameters
• in node facts repo : there is nothing to change, there is a callback that triggers the policy generation
• during policy generation we want to sync all with the UI (this unveils the dependency between “generation” and “properties status”, it is only more explicit now), and we do it after the update of dynamic groups, and before querying the updated properties in the repo : we were already doing that previously

TODO

Calls are blocking and may add significant processing time for every method on repos. We need to take into account that the properties computation may be expensive.

This design may lead to repeated calls in the same logical unit (e.g. when updating global parameters from the UI, the UI calls both the global parameters repo and triggers a policy generation), and we will likely have concurrent calls to the same properties computation that may be expensive. But we mostly want the update to be non-blocking.

So we need to change the semantic of the updateAll in the repository calls to be non-blocking, and policy generation (and syncProperties that it uses) needs it to be semantically blocking. For that we use a dropping queue with 1 element, and expose a blocking method for the case when blocking is needed.

[clarktsiory]

PR updated with a new commit

[clarktsiory]

PR updated with a new commit

[clarktsiory]

PR updated with a new commit