fix(eks-monitoring): kube-proxy scrape config and alert rule

[youwalther65]

What does this PR do?

It removed the current kube-proxy related OTEL scrape job and replaced it with a working one. With a working kube-proxy scrape job it is possible to use KubeProxyDown Prometheus alert rule again.

Motivation

kube-proxy is an important data plane component to monitor

More

• [x] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• [x] Yes, I ran pre-commit run -a with this PR
• [ ] Yes, I have added a new example under examples to support my PR (when applicable)
• [ ] Yes, I have updated the Pages for this feature

Note: Not all the PRs required examples and docs.

For Moderators

• [ ] E2E Test successfully complete before merge?

Additional Notes

As discussed with @bonclay7 we will make this a default.

[bonclay7]

Thanks @youwalther65, will the dashboard come in another PR? (post build variables for Kustomization)