Modify NodeNames in AWS jobs

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!--> ## Context In the GCE jobs, the nodes are given well-defined names (like “us-east-1-a”) and so the per-node metrics have well-defined labels, so they can easily be compared across days. Whereas in the AWS job, the nodes seem to have randomly-assigned names, and so the metrics labels end up being different every day so we can't compare them as easily. Example: - NodeName in GCE test: `name: control-plane-us-east1-b-jlvv`, `control-plane-us-east1-b-smv6` - NodeName in AWS test have different namings. **What you expected to happen**: The node metrics don't have consistent trends over time. As a result, overtime GCE tests have a trend https://perf-dash.k8s.io/#/?jobname=gce-5000Nodes&metriccategoryname=E2E&metricname=LoadResources&PodName=kube-proxy-nodes-us-east1-b%2Fkube-proxy&Resource=memory <img width="1286" height="847" alt="Image" src="https://github.com/user-attachments/assets/19279c08-6e75-4eee-be75-c426c525b16d" /> AWS jobs don't have a trend because they are using different node names. https://perf-dash.k8s.io/#/?jobname=aws-5000Nodes&metriccategoryname=E2E&metricname=LoadResources&PodName=kube-proxy-i-094de2c600c60d0bb%2Fkube-proxy&Resource=memory <img width="1289" height="850" alt="Image" src="https://github.com/user-attachments/assets/55512119-cffb-45a8-9178-e82da2a8b6b6" /> Context in sig-scalability: https://kubernetes.slack.com/archives/C09QZTRH7/p1771436311523919