[EKS-AutoMode] [Feature Request]: Dynamic Instance Naming on AWS EC2 Console for EKS Auto Mode Cluster instances with Shared NodeClass

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

### Current Behavior
- Multiple NodePools are sharing the same NodeClass configuration in EKS auto mode cluster
- Unable to implement dynamic instance naming using variables in NodeClass configuration
- Current attempted NodeClass configuration:
---
```
spec:
tags:
Name: -
```
---

### Expected Behavior

- Ability to dynamically set instance Name tags based on respective NodePool names
Each NodePool should have its instances tagged with unique names while sharing the same NodeClass
Use Case

We need to configure custom instance naming in AWS Console
Instance names should reflect both cluster name and NodePool name
Multiple NodePools are using shared NodeClass configuration

### Questions

1. Is there a supported method to achieve dynamic tagging in EKS Auto mode when NodePools share the same NodeClass?
2. Can variables be used to reference NodePool names in the NodeClass configuration?

### Additional Context
- Cluster name can be hardcoded if needed
- The main challenge is dynamically incorporating the NodePool name in the instance tags
Environment

Service: Amazon EKS
Feature: Auto Mode Cluster
Component: NodeClass Configuration

Start with the EKS Auto Mode NodeClass configuration and AWS EC2 instance-tag behavior described in the issue. Determine how shared NodeClasses relate to NodePools and whether NodePool names can be resolved in tags. Done means the dynamic naming behavior is implemented and verified for multiple NodePools, or the supported limitation and alternative are documented.

Written by the indexing model from the issue text.