Add Parsers for Various Benchmark Variants from PerfNext, Perffarm & Adopt

### Problem Description

Currently, TRSS supports parsing of both PerfNext and Perffarm jobs. While PerfNext builds that use Jenkins are parsed right away after runs are done, Perffarm builds are parsed when Perf Compare is used.

While TRSS does have some parsers, it doesn't have benchmark parsers for many of the benchmark variants that exist on PerfNext and Perffarm, configurations that are used frequently. As a result, we need to manually parse them for the time being.

Furthermore, even if we have parsers for some configs, we parse only some metrics and haven't added support for others, which might be important to get full performance evaluation of a build.

Some of these configs were newly added to launcher tools in order to support new variants and benchmark versions. Also, parsers could have been missed for some of the less popular benchmark variants, something that we should still add in order to extend coverage.

### Benchmark Parsers to Add

**Perffarm & PerfNext:**
- Different Startup and throughput variants for Liberty
- Various ODM variants
- HiBench
- SPECjbb2015
- Any other missing

**Adopt:**

- BumbleBench
- Dacapo
- Idle Micro
- Liberty
- Renaissance

### Proposed Changes

- Add new Perffarm variants to [BenchmarkVariants](https://github.com/AdoptOpenJDK/openjdk-test-tools/blob/master/test-result-summary-client/src/PerfCompare/lib/benchmarkVariantsInfo.js).
- Add new PerfNext variants to [BenchmarkMetricRouter](https://github.com/AdoptOpenJDK/openjdk-test-tools/blob/master/TestResultSummaryService/parsers/BenchmarkMetricRouter.js
) and [BenchmarkMetric](https://github.com/AdoptOpenJDK/openjdk-test-tools/blob/master/TestResultSummaryService/parsers/BenchmarkMetric.js). PerfNext configs can be found [here](https://github.com/AdoptOpenJDK/openjdk-test-tools/tree/master/PerfNext/config/benchmarks/data_simple).

### Assigned Contributors
I'll be working with Dong (@dhlee49) from my team to work on this design.

Start by comparing the benchmark configurations in PerfNext/config/benchmarks/data_simple with existing entries in test-result-summary-client/src/PerfCompare/lib/benchmarkVariantsInfo.js, TestResultSummaryService/parsers/BenchmarkMetricRouter.js, and BenchmarkMetric.js. Review which PerfNext, Perffarm, and Adopt variants and metrics are already covered. Done means the listed benchmark variants can be parsed and their relevant metrics are represented in the appropriate parser mappings.

Written by the indexing model from the issue text.