[EKS] [eks-pod-identity-agent:][request]: Add support for configuring EKS Pod Identity Agent metrics through managed addon configuration

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Add support for configuring EKS Pod Identity Agent metrics through the managed addon configuration in the AWS Console. Currently, this can only be done using Helm, which limits the ease of use for customers who prefer using the AWS Console for management.

**Which service(s) is this request for?**
Amazon EKS (Elastic Kubernetes Service)

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
As of last week, EKS Pod Identity supports metrics starting from version [eks-pod-identity-agent:v0.1.20](https://github.com/aws/eks-pod-identity-agent/pull/46). However, the current managed addon configuration schema doesn't provide direct support for enabling metrics through the addon configuration in the AWS Console.

This limitation makes it difficult for customers who prefer using the AWS Console to manage their EKS clusters. They are unable to take advantage of the new metrics feature without resorting to Helm, which may be outside their usual workflow or expertise.

The impact of not solving this problem is reduced visibility into the performance and health of the Pod Identity Agent for customers who rely on the AWS Console. It also creates an inconsistent experience between console users and those who use Helm, potentially leading to confusion and increased support requests.

**Are you currently working around this issue?**
Currently, the only workaround is to use Helm to configure the metrics. Customers need to apply the following Helm values:

```yaml
metrics:
enabled: true
port: 2705
path: /metrics
extraLabels:
prometheus.io/scrape: "true"
prometheus.io/port: "2705"
```

**Additional context**
NA

**Attachments**
NA

Start by reviewing the EKS managed addon configuration schema and the eks-pod-identity-agent Helm values described in the issue. Done means metrics can be enabled and configured through the managed addon configuration in the AWS Console, including the port, path, and extra labels.

Written by the indexing model from the issue text.