[EKS]: name Amazon EKS add-ons Consistently (i.e. choose "Amazon" or "AWS")

### 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**

I would like it if Amazon/AWS utilized consistent naming for their Amazon EKS add-ons.

**Which service(s) is this request for?**

EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

The problem I'm trying to solve is:

- lack of standards within the Amazon/AWS organization
- lack of cohesion in branding with would/should damages the brand (it makes the company look like a bunch of clowns <- ask a marketing person)
- a perception that the teams at Amazon/AWS don't work together (i.e. the just build products without any overarching guidance) and makes customers fully aware of the failure of "two pizza teams"
- putting a stop to the inconsistent naming so the problem doesn't get worse

**Are you currently working around this issue?**

I choose either the Amazon or AWS add-on.

**Additional context**

I spend extra cycles being frustrated that Amazon/AWS can't get naming right.

**Attachments**

identifiable information.)

Start by reviewing the EKS add-on names covered by the request and the attached naming example. Done would require an agreed Amazon/AWS convention and corresponding naming updates; the issue identifies no files, tests, or implementation entry points.

Written by the indexing model from the issue text.