Centralized constants file for docker Images in Jenkinsfile

[abhinavGupta16]

Is your feature request related to a problem? Please describe

Currently, the image file is mentioned as a hardcoded string in every jenkinsfile. Any change or upgrade in the image is difficult since we would have to manually go to every jenkinsfile and edit the docker image.

This Manual process makes it easy to miss a file causing unwanted errors when running jobs such as these - http://jenki-jenki-fpgmrv2ryxko-1366042710.us-east-1.elb.amazonaws.com/job/opensearch-java-maven-sign-and-release/4/console

Describe the solution you'd like

One constants file which contains all the docker images used in every jenkinsfile. This would make it one point change for nay changes in the image. Any new additional image can be easily added to this file.

Acceptance Criteria

• No jenkinsfile should have the image name hardcoded as a string.
• All jenkins jobs should work as before

Describe alternatives you've considered

No response

Additional context

No response

[dblock]

This makes docker images a moving target implicitly, whereas in the manifests we want something that can be reproduced indefinitely. The ask here is a subset of #1207: one should be able to write ubuntu-latest vs. specific-docker-image in both manifests and other Jenkinsfile(s), thus expressing intent of which image to use clearly.

[zelinh]

[Triage] Moving to product backlog, part of issue #1207 and we will discuss how we want to proceed.

[gaiksaya]

Related #4233