[operator] Manage Gardener Dashboard

[rfranzke]

How to categorize this PR?

/area usability
/kind enhancement

What this PR does / why we need it:
With this PR, gardener-operator manages the Gardener Dashboard.

Special notes for your reviewer:
/cc @petersutter @grolu @holgerkoser

Note

You can test it locally by running make kind-operator-up operator-up and then kubectl apply -f example/operator/20-garden.yaml.

Release note:

`gardener-operator` is now managing the Gardener Dashboard when `.spec.virtualCluster.gardener.gardenerDashboard` is set in the `Garden` resource. Read more about it [here](https://github.com/gardener/gardener/tree/master/docs/concepts/operator.md#dashboard)

[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

[rfranzke]

/cc @ScheererJ

[gitguardian]

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Generic High Entropy Secret	85e8f76	pkg/component/gardener/dashboard/dashboard_test.go	View secret
-		Generic High Entropy Secret	02f5a1d	pkg/component/gardener/dashboard/dashboard_test.go	View secret
-		Generic High Entropy Secret	85e8f76	pkg/component/gardener/dashboard/dashboard_test.go	View secret
-		Generic High Entropy Secret	02f5a1d	pkg/component/gardener/dashboard/dashboard_test.go	View secret
-		Generic High Entropy Secret	85e8f76	pkg/component/gardener/dashboard/dashboard_test.go	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[ScheererJ]

/assign

[petersutter]

/lgtm 🥳

[gardener-prow]

LGTM label has been added.

Git tree hash: 56729f9386b2f20a1d512d04e1e139f8243ef728

[rfranzke]

/approve

[gardener-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petersutter, rfranzke

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rfranzke]

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