gardenctl: matoleo yote na matoleo ya zamani

# [github.com/gardener/gardenctl-v2:v2.19.1]

## 🏃 Others
• `[USER]` `v2.19.1` supersedes the incomplete [`v2.19.0` release](https://github.com/gardener/gardenctl-v2/releases/tag/v2.19.0) after a transient upload failure prevented publishing its binaries and package updates. It contains no additional functional changes; see the linked release for the changes since `v2.18.0`. by `@federated-github-access[bot]` [[#863](https://github.com/gardener/gardenctl-v2/pull/863)]

# [github.com/gardener/gardenctl-v2:v2.18.0]

## 🏃 Others
• `[DEPENDENCY]` Bump go version to v1.27.3 by `@gardener-ci-robot` [[#809](https://github.com/gardener/gardenctl-v2/pull/809)]

# [github.com/gardener/gardenctl-v2:v2.17.0]

## ✨ New Features
• `[USER]` Add the `gps` alias to `gardenctl rc` to configure the provider CLI with the targeted shoot’s infrastructure credentials, even when its control plane is selected. This complements `gpc`, which uses the infrastructure credentials of the seed hosting that control plane. by @julestree [[#831](https://github.com/gardener/gardenctl-v2/pull/831)]
• `[USER]` Support seed targeting via a `seed` named capturing group in targeting patterns. by @petersutter [[#802](https://github.com/gardener/gardenctl-v2/pull/802)]

## 🐛 Bug Fixes
• `[USER]` PowerShell provider environment scripts no longer require a POSIX `printf` executable for revoke hints and access-restriction notifications. by @grolu [[#838](https://github.com/gardener/gardenctl-v2/pull/838)]

[github.com/gardener/gardenctl-v2:v2.15.0]
✨ New Features
• [OPERATOR] gardenctl now supports requesting a read-only viewer kubeconfig instead of admin via the --access-level flag (admin / viewer / auto) and the per-garden kubeconfigAccessLevelDefaults.{shoots,managedSeeds} config block (also editable via gardenctl config set-garden). by @jamand [#735]
• [OPERATOR] gardenctl provider-env and gardenctl ssh now support --control-plane for shoot targets backed by a managed seed, operating on the seed infrastructure instead of the workload shoot. A new gpc alias is provided as a shortcut for provider-env --control-plane. by @petersutter [#760]
🐛 Bug Fixes
• [USER] The gardenctl ssh command now validates node addresses before use. by @petersutter [#776]

[github.com/gardener/gardenctl-v2:v2.15.0]
✨ New Features
- [OPERATOR] gardenctl now supports requesting a read-only viewer kubeconfig instead of admin via the --access-level flag (admin / viewer / auto) and the per-garden kubeconfigAccessLevelDefaults.{shoots,managedSeeds} config block (also editable via gardenctl config set-garden). by @jamand [#735]
- [OPERATOR] gardenctl provider-env and gardenctl ssh now support --control-plane for shoot targets backed by a managed seed, operating on the seed infrastructure instead of the workload shoot. A new gpc alias is provided as a shortcut for provider-env --control-plane. by @petersutter [#760]
🐛 Bug Fixes
- [USER] The gardenctl ssh command now validates node addresses before use. by @petersutter [#776]

[github.com/gardener/gardenctl-v2:v2.14.0]
✨ New Features
- [USER] gardenctl target view now also displays the seed, if a shoot was targeted. by @dguendisch [#712]
📖 Documentation
- [USER] Describe installation using winget instead of chocolatey by @mbs-c [#726]
- [USER] Recommend the rc command for configuring the shell in README.md by @mbs-c [#727]

[github.com/gardener/gardenctl-v2:v2.13.0]
✨ New Features
- [USER] ssh: Bastion ingress addresses and hostnames are now validated to prevent invalid IP addresses and non-DNS-compliant hostnames. by @petersutter [#678]
- [USER] Added sanity checks for user-provided and shoot node SSH keys by @petersutter [#674]
- [USER] The gardenctl ssh command now accepts a --shell flag to specify the shell used for escaping arguments when printing SSH commands. If not provided, it falls back to the GCTL_SHELL environment variable or defaults to bash. To set GCTL_SHELL automatically, source the gardenctl startup script in your shell profile (e.g., add source <(gardenctl rc bash) to ~/.bashrc), or use the --shell flag to avoid escaping issues. by @petersutter [#690]
- [USER] provider-env: Added workload identity support for provider environments on AWS, Azure, and GCP. Use the --workload-identity-token-expiration flag to control token validity duration (default: 1h). by @petersutter [#659]