Consider update group on applying changes to keep provenance information

[MartinWeindel]

How to categorize this PR?

/kind enhancement

What this PR does / why we need it:
The DNS controller manager assumes that it doesn't matter which set of credentials is used for a specific zone if different credentials are used for different DNSProviders.
This assumption can lead to the loss of the correct provenance information on updates if the backend supports it (like PowerDNS).

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

Consider update group on applying changes to keep provenance information

[gardener-prow]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[gardener-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign marc1404 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[MartinWeindel]

cc @Lappihuan

[MartinWeindel]

/test all

[MartinWeindel]

/test all

[MartinWeindel]

/hold needs more testing

[Lappihuan]

I tested this PR in our staging environment and can confirm it resolves the issue.

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close

/lifecycle rotten

[marc1404]

/remove-lifecycle rotten

[gardener-ci-robot]

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

• After 15d of inactivity, lifecycle/stale is applied
• After 15d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 7d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Mark this PR as rotten with /lifecycle rotten
• Close this PR with /close

/lifecycle stale

[Lappihuan]

We still had some edge cases that weren’t fixed by this PR. @MartinWeindel informed me that it wouldn’t be feasible to integrate these fixes into the current controllers, but the rewrite will automatically handle this use case.
Therefore, we can safely close this PR and wait for dnsman2.

[MartinWeindel]

/close will be addressed in context of new implementation "dnsman2"