How to categorize this issue?

/area usability
/area dev-productivity
/area documentation
/kind bug

What happened:
When deploying Gardener locally as described in getting_started_locally_with_extensions.md and NOT using workload identity I get errors for missing config options, e.g.:

Check if essential config options are initialized
".metadata.namespace" in file "go/src/github.com/gardener/gardener/example/provider-extensions/garden/project/credentials/infrastructure-workloadidentities.yaml" is empty or does not exist. Please check your config.
make: *** [gardener-extensions-up] Error 1

What you expected to happen:
It should deploy without requiring config options in files related to workload identities.

How to reproduce it (as minimally and precisely as possible):
Prepare all files required for local deployment mentioned in the above doc including static provider credentials in

• /example/provider-extensions/garden/controlplane/domain-secrets.yaml
• /example/provider-extensions/garden/project/credentials/infrastructure-secrets.yaml
• /example/provider-extensions/garden/project/credentials/secretbindings.yaml

and do make gardener-extensions-up

Anything else we need to know?:

Environment:

• Gardener version: v1.125.0
• Kubernetes version (use kubectl version): v1.33.3
• Cloud provider or hardware configuration:
• Others: