Fix windows feature tests

[movence]

rev:

• make java setup powershell scripts block to its own more readable script file
• switch hardcoded dependency (jar) versions into variables for easier management
• new run: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/20309735550

Description of the issue

Windows feature test is failing due to hardcoded JDK (15.0.2) path while integ test AMI uses OpenJDK 17.0.2

null_resource.integration_test_run_validator[0] (remote-exec): Start-Process : This command cannot be run due to the error: The system cannot find the file specified.
null_resource.integration_test_run_validator[0] (remote-exec): At line:1 char:1
null_resource.integration_test_run_validator[0] (remote-exec): + Start-Process -FilePath "C:\Program Files\OpenJDK\jdk-15.0.2\bin\java ...
null_resource.integration_test_run_validator[0] (remote-exec): C:\Users\Administrator>powershell.exe -Command "Start-Process -FilePath \"C:\Program Files\OpenJDK\jdk-15.0.2\bin\java.exe\" -ArgumentList \"-javaagent:C:\jmx_workload\jmx_prometheus_javaagent-0.12.0.jar=9404:C:\jmx_workload\exporter_config.yaml -cp C:\jmx_workload\SampleJavaApplication-1.0-SNAPSHOT.jar com.gubupt.sample.app.App\""
null_resource.integration_test_run_validator[0] (remote-exec): + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

link

Description of changes

• Update java process start step to search JDK path dynamically
• Add retry when checking JMX metrics endpoint availability

License

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

Tests

https://github.com/aws/amazon-cloudwatch-agent/actions/runs/20236019893

[musa-asad]

Should we run the Windows Workload Discovery / SSM document tests too? Just to ensure nothing broke there.

[movence]

They all share the same terraform files so that's why I added restart test in my last run https://github.com/aws/amazon-cloudwatch-agent/actions/runs/20236019893