Revert "[Java] Custom Metrics E2E Test (#479)"

[Miqueasher]

This reverts commit 6d1ff60.

Java main build fails custom metric validation test in default-v8-amd64 & default-v23-amd64 for an unknown reason (see here). Custom metric PR #479 needs to be reverted so it is not blocking any future runs of the Java Main Build.

Description of changes:

Once the solution to those 2 test cases is fixed this will be reverted along with the solution to the problem being added to that PR.

<Can we safely revert this commit if needed? If not, detail what must be done to safely revert and why it is needed.>
If necessary to revert we can revert this commit, but if the solution to the failure for those 2 test cases isn't found they will fail again.

Ensure you've run the following tests on your changes and include the link below:

To do so, create a test.yml file with name: Test and workflow description to test your changes, then remove the file for your PR. Link your test run in your PR description. This process is a short term solution while we work on creating a staging environment for testing.

NOTE: TESTS RUNNING ON A SINGLE EKS CLUSTER CANNOT BE RUN IN PARALLEL. See the needs keyword to run tests in succession.

• Run Java EKS on e2e-playground in us-east-1 and eu-central-2
• Run Python EKS on e2e-playground in us-east-1 and eu-central-2
• Run metric limiter on EKS cluster e2e-playground in us-east-1 and eu-central-2
• Run EC2 tests in all regions
• Run K8s on a separate K8s cluster (check IAD test account for master node endpoints; these will change as we create and destroy clusters for OS patching)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.