Update Helm release crossplane to v2.0.6 (main)

This MR contains the following updates:

Package	Update	Change
crossplane (source)	patch	2.0.4 -> 2.0.6

---

⚠️ Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

crossplane/crossplane (crossplane)

v2.0.6

Compare Source

This release resolves #​6761 - issues when upgrading providers that manifest with errors like these:

cannot establish control of object: addresses.compute.gcp.upbound.io is already controlled by ProviderRevision provider-gcp-compute-a41e4ba551fc (UID 58db5de-38e7-40f9-9d31-669bb25a688e)

What's Changed

• [Backport release-2.0] Use server-side apply for MRD controller by @​negz in #​6953

Full Changelog: https://github.com/crossplane/crossplane/compare/v2.0.5...v2.0.6

v2.0.5

Compare Source

What's Changed

• chore(deps): update module golang.org/x/crypto to v0.43.0 [security] (release-2.0) by @​crossplane-renovate[bot] in #​6923
• [Backport release-2.0] Fix XRD controller watch startup after transient failures by @​negz in #​6930
• [Backport release-2.0] Fix claim controller watch startup after transient failures by @​github-actions[bot] in #​6932
• [Backport release-2.0] fix: Add TLS as app protocol to function service by @​github-actions[bot] in #​6945
• chore(deps): update module golang.org/x/crypto to v0.45.0 [security] (release-2.0) by @​crossplane-renovate[bot] in #​6939

Full Changelog: https://github.com/crossplane/crossplane/compare/v2.0.4...v2.0.5

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• If you want to rebase/retry this MR, check this box

---

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)