Support for sequential Conduit updates

[zolug]

Is your feature request related to a problem? Please describe.
When multiple Conduits are updated at once (for example part of a version upgrade) it might be desirable to serialize these updates so that only 1 Conduit would be affected at a time. This could be beneficial for example if 2 Conduits are used to accomplish a communication model with a "primary" and a "secondary" fallback path.

Describe the solution you'd like
The feature should be implemented in the Operator. Conduit Custom Resources could be optionally grouped based on the value of a dedicated annotation. By using a locking mechanism, the Operator could ensure that only one Conduit from the same group processes updates at a time.

Describe alternatives you've considered
The Conduit Custom Resource mostly translates to a DaemonSet implementing the Proxy logic. There seems to be no kubernetes native way of coordinating updates between separate DaemonSets.