Leftover Secret resources in kube-system after uninstalling Envoy Gateway

Describe the bug
When Envoy Gateway is uninstalled (or the corresponding Helm chart/addon is removed), several Secret resources created in the kube-system namespace are not properly cleaned up and remain in the cluster.

To Reproduce
Steps to reproduce the behavior:

Install Envoy Gateway.

Uninstall Envoy Gateway (e.g., via Helm, egctl, or platform addon manager).

Check remaining secrets in kube-system:

Bash
kubectl get secret -n kube-system | grep envoy
Expected behavior
All resources generated by Envoy Gateway, including internal and component secrets in kube-system, should be completely removed upon uninstallation or handled via proper cleanup hooks / finalizers.

Actual behavior
The following secrets remain orphaned in the kube-system namespace:

Plaintext
NAME TYPE DATA AGE
envoy kubernetes.io/tls 3 4h4m
envoy-gateway kubernetes.io/tls 3 4h4m
envoy-oidc-hmac Opaque 1 4h4m
envoy-rate-limit kubernetes.io/tls 3 4h4m
Environment
Envoy Gateway Version: 1.7.2

Reproduce the uninstall using Helm, egctl, or the platform addon manager, then run `kubectl get secret -n kube-system | grep envoy` to inspect the leftover resources. Trace how the `envoy`, `envoy-gateway`, `envoy-oidc-hmac`, and `envoy-rate-limit` Secrets are created and owned; done means they are removed after Envoy Gateway is uninstalled.

Written by the indexing model from the issue text.