Manage zone state caches globally

[MartinWeindel]

What this PR does / why we need it:
Currently, the zone state caches are managed per internal DNSAccount object.
A DNSAccount object is created per set of credentials as it is not possible to identify the account for all provider types.
If there are now multiple credentials for the same account, e.g. because of credentials rotation, there are multiple DNSAccount instances with separate zone state caches for the same hosted zone(s).
The updates are always executed using the account of the provider of the DNSEntry. But all these updates are performed during a zone reconciliation by comparing to a single cached zone state from one account. This can lead to phantom or missing records in this particular cache and update operations are added to "repair" the mismatches. These update operations will fail und the updates are added on the next reconciliation again until the zone state caches is synchronised periodically.

Using the newly introduced qualified zone ids, the zone state caches are now managed globally. This means there is only one zone state cache per hosted zone globally, independent of the number of DNSAccounts.

Addtionally the option to store the caches in a persistent volume has been removed, as it was never used and adjusting it to the new structure was too much effort.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

Manage zone state cache globally

Persisting zone state caches with option `--cache-dir` is not supported anymore.

[gardener-robot]

@mandelsoft You have pull request review open invite, please check