Generated manifests for OpenSearch 2.x need custom JAVA_HOME

[dblock]

Is your feature request related to a problem? Please describe

Automation opened a PR to generate the OpenSearch 3.0 manifest. That manifest was missing JAVA_HOME that was added manually in #2042.

Describe the solution you'd like

Add a way to customize generated manifests for various products/versions, add JAVA_HOME to the OpenSearch ones.

Describe alternatives you've considered

Keep doing it manually.

Additional context

No response

[peterzhuamazon]

We just need the manifest workflow to add this line for OpenSearch BE.
The problem being we can only default to the highest java version tho.

[dblock]

There's some hard-coding going on in

opensearch-build/src/manifests_workflow/input_manifests.py

Line 108 in 3b65a0a

def create_manifest(self, version: str, components: List = []) -> InputManifest:

that will need refactoring.

[prudhvigodithi]

[Triage] just a thought since the the build container already has multiple java versions added, we might need to add an entry to manifest file that has JDK version specification, just like we have one for checks:, so that way each component can use the desired java version that is passed, if not it will go withe default JDK version.

[zelinh]

Instead of hard-coding both image_map, jdk_version and data: Dict = ..., we are looking into an alternative way to auto generate the manifest with those data. As @dblock suggested here, I will be trying to create such template manifest folders and have the new manifest loading those infos depending on the product and version. If it doesn't have certain template, we will use hard-coded default value.

[gaiksaya]

Closing via #2358