[release v1.68] update g/g to v1.136.6

[AndreasBurger]

How to categorize this PR?

/area compliance
/kind task
/platform aws

What this PR does / why we need it:
Updates g/g to include a bugfix (See gardener/gardener#14189)

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

Release note:

updated github.com/gardener/gardener to v1.136.6

[github-actions]

This change updates several Go module dependencies to their newer versions, including core Gardener components and the standard library networking package. The updates appear to be routine maintenance to incorporate latest bug fixes and improvements.

Walkthrough

• Chore: Updated github.com/gardener/etcd-druid/api from v0.35.0 to v0.35.1 for latest etcd management improvements
• Chore: Upgraded github.com/gardener/gardener from v1.136.2 to v1.136.6 incorporating recent Kubernetes cluster management enhancements
• Chore: Bumped golang.org/x/net from v0.50.0 to v0.51.0 for updated networking libraries and security patches

These dependency updates ensure the application benefits from the latest stability improvements and security fixes in the Gardener ecosystem and Go standard library.

_{Model: claude-sonnet-4-20250514 | Prompt Tokens: 2294 | Completion Tokens: 209}

[wpross]

/lgtm

[gardener-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wpross

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [wpross]

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

[gardener-prow]

LGTM label has been added.

Details

Git tree hash: 27986fed6d291f1579e453bee48a1a666a9cd6e5

[matthias-horne]

/cherrypick master

[gardener-ci-robot]

@matthias-horne: new pull request created: #1748

Details

In response to this:

/cherrypick master

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.