Possible CVE fixes by Jenkins core upgrade

[jordarlu]

Is your feature request related to a problem? Please describe

This is a consolidated issue to aggregate all CVEs that could be resolved by next Jenkins core upgrade
The list could be updated accordingly...

#3338 - spring-expression-5.3.24.jar
#3396 - spring-expression-5.3.24.jar
#3672 - jenkins-core-2.387.1.jar
#3673 - guava-31.1-jre.jar
#3832 - jenkins-core-2.387.1.jar
#4082 - jenkins-core-2.387.1.jar
#4081 - jenkins-core-2.387.1.jar
#4080 - jenkins-core-2.387.1.jar
#4078 - jenkins-core-2.387.1.jar
#4077 - jenkins-core-2.387.1.jar
#4406 - jenkins-core-2.387.1.jar
#4404 - jenkins-core-2.387.1.jar
#4589 - jenkins-core-2.387.1.jar
#4630 - jenkins-core-2.387.1.jar

Describe the solution you'd like

Next Jenkins core upgrade https://www.jenkins.io/changelog/

Determine the breaking changes with respect to jenkins as well as all its plugins in use.
See opensearch-project/opensearch-ci#333 for details on upgrade cycle.

Describe alternatives you've considered

No response

Acceptance Criteria

• Jenkins should retain all previous data
• Jenkins should be upgraded to a newer version
• Upgrade jenkis core version in all build.gradle files to resolve the CVEs
• Track new CVEs related to new upgraded version

[jordarlu]

@peterzhuamazon @gaiksaya

[peterzhuamazon]

Thanks Jeff.

[jordarlu]

Updating the possible CVE fixes list in case description by upgrading the Jenkins Core to the latest version.

[peterzhuamazon]

Need to also upgrade the Jenkins with monitoring plugin:

• Jenkins main node has very high cpu and mem usages opensearch-ci#346 (comment)

[rishabh6788]

Plan to add monitoring plugin in the week of 25th-Sept.
cc: @peterzhuamazon @prudhvigodithi

[jordarlu]

list has been updated