EKS authorization using aws-auth ConfigMap is deprecated

The page https://docs.aws.amazon.com/eks/latest/userguide/auth-configmap.html has a note:

> The aws-auth ConfigMap is deprecated. For the recommended method to manage access to Kubernetes APIs, see [Grant IAM users access to Kubernetes with EKS access entries](https://docs.aws.amazon.com/eks/latest/userguide/access-entries.html).

It would be nice to setup authorization using EKS Access Entries in this sample project.
That would also result in a simpler code.

Start by searching the repository for the aws-auth ConfigMap and the EKS or Kubernetes deployment configuration. Read the EKS access entries documentation linked in the issue, then determine which sample resources and deployment steps must change; done means the sample uses access entries, no longer relies on aws-auth, and remains deployable.

Written by the indexing model from the issue text.