Use appropriate Jenkins agent label for benchmark test

[rishabh6788]

Currently the benchmark job runs on Jenkins agent label Jenkins-Agent-AL2-X64-M52xlarge-Docker-Host-Benchmark-Test. The naming convention suggests that the process runs inside a docker container on the AL2 host when actually the job runs on the host directly.
Create new jenkins agent with label Jenkins-Agent-AL2-X64-M52xlarge-Host-Benchmark-Test and use that for benchmarking job in future.

[peterzhuamazon]

Note sure if we need a new agent, but rename would help a lot.

[gaiksaya]

The label string is changed to Jenkins-Agent-AL2023-X64-M52xlarge-Benchmark-Test
https://github.com/opensearch-project/opensearch-ci/blob/main/lib/compute/agent-nodes.ts#L135

Closing this issue!

[peterzhuamazon]

Handled by this:

• [Windows Container] Add #337 #338 AMI and add new customDeviceMapping config with new benchmark agent opensearch-ci#339