[BUG] Security Integ Tests are failing due to Container NodeJS version

[dbwiddis]

What is the bug?

Security integ tests are failing; the docker container isn't starting up.

/usr/bin/docker exec  dd8724fb2148734b9a8dc02393616f99f1bbc99e984a4a589451b9315fc17862 sh -c "cat /etc/*release | grep ^ID"
/__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /__e/node20/bin/node)
/__e/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /__e/node20/bin/node)

This is known behavior for several months that occurred on NodeJS 20, and was temporarily worked around by downgrading actions/checkout to v3 which still used Node16.

However, GitHub recently switched all their runners to Node20 which invalidated this workaround.

How can one reproduce the bug?

Submit a PR.

What is the expected behavior?

Tests pass.

Do you have any additional context?

It looks like the build team is well aware of this:

• [Deprecation] Properly deprecate CentOS7 as CI build image/Supported OS and switch to Almalinux8 opensearch-build#4379

And this PR by @peterzhuamazon may fix it:

• Move CentOS7 build image to legacy opensearch-build#4820

We should still upgrade the test's actions/checkout to the latest version (v4) since v3 is deprecated and the v3 downgrade is no longer effective. (Done in #757.)

[dbwiddis]

Looks like a temporary workaround:

• Fix linux build CI error due to action runner env upgrade node 20 k-NN#1795