Use consistent extension naming across extension lists

[BoHristova]

Why is the issue needed

On the website, there are two different places listing Gardener extensions – the website section List of Extensions and the section Known Extension Implementations.

The naming of extensions is inconsistent between the two lists. For example, the extension implemented in gardener/gardener-extension-shoot-networking-filter is referred to as "Egress Filtering" in List of Extensions and as "Shoot Networking Filter" in Known Extension Implementations.

These inconsistencies make it harder for users to identify, search for, and navigate between extensions.

Here's a comparison table between the names used in the two lists:

Website title	README name	Match?
Infrastructure Provider
Provider Alibaba Cloud	Alicloud	✗
Provider AWS	AWS	✗
Provider Azure	Azure	✗
Provider GCP	GCP	✗
Provider IronCore	IronCore	✗
Provider IronCore Metal	IronCore Metal	✗
Provider metal-stack	metal-stack	✓
Provider OpenStack	OpenStack	✗
Provider STACKIT	STACKIT	✗
Operating System
CoreOS/FlatCar OS	CoreOS/FlatCar	✗
Garden Linux OS	GardenLinux	✗
SUSE CHost OS	SuSE CHost	✗
Ubuntu OS	Ubuntu	✗
Container Runtime
GVisor container runtime	gVisor	✗
Network Plugin
Calico CNI	Calico	✗
Cilium CNI	Cilium	✗
Generic/Others
Access Control List Extension	ACL	✗
Kubernetes Auditing	Auditing (\gardener/gardener-extension-auditing`)`	✗
Registry Cache	Registry Cache	✓
Certificate Services	Shoot Certificate Service	✗
DNS Services	Shoot DNS Service	✗
Lakom Service	Shoot Lakom Service	✗
Egress Filtering	Shoot Networking Filter	✗
Networking Problem Detector	Shoot Networking Problem Detector	✗
OpenID Connect Services	Shoot OpenID Connect Service	✗
Node Audit Logging	Shoot Rsyslog Relp	✗
Traefik Ingress	Shoot Traefik	✗

What would you like to be added

The names of the extensions in the list of Known Extension Implementation should match the names in the List of Extensions website section, so that the same extension is referenced consistently across the website.