Added eks-aperf.sh, Dockerfile and README-EKS.md for EKS instructions

[salvatoredipietro]

Description of changes:

Added Kubernetes support for running APerf on Amazon EKS clusters with three new files:

• Dockerfile to build a containerized version of APerf with multi-architecture support (x86_64/arm64)
• eks-aperf.sh script to deploy and run APerf pods on specific EKS nodes
• README-EKS.md with detailed setup instructions and usage examples

This enhancement enables collecting performance metrics on EKS nodes without requiring direct SSH access, making it easier to profile applications running in Kubernetes environments.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[DDxPlague]

these look good to me. Tested it on my cluster with you and got good results.

[CristianPrundeanu]

Recommend to factor out the parsing so you have less code and don't have to repeat each argument.

Example:

while [ $# -gt 0 ]; do
    dest=""
    case "${1%=*}" in
        --foo) dest=SET_FOO;;
        --bar) dest=SET_BAR;;
        *) echo "Unknown parameter: $1"; exit 1;;
    esac
    if [[ "$1" = *=* ]]; then 
        let ${dest}="${1#*=}"
    else 
        let ${dest}="$2"
        shift
    fi  
    shift
done

[CristianPrundeanu]

Should we name the report at generate time instead of here (or even allow the user to define the name), to avoid ending up with multiple reports with the same internal name?