[ETL-671] Update to use older node version on aws actions

[rxu17]

Purpose: This is a draft PR because this is just a temp. solution. There is a known discrepancy between the glibc version used by the aws glue docker images (2.26) and glibc version used by all of the AWS actions versionswhich is expecting >= 2.27. Until the aws glue docker images are updated to use Node js version 20 (which uses glibc >= 2.27), this is the discovered workaround. See blog post for more info. This discussion gives a good view into the issue itself: actions/checkout#1809 (comment)

This solution is still temp. because ideally aws updates their aws glue docker images to use node js 20.

See JIRA ticket comments for more detailed updates on what was tried

Testing: Our GH actions for aws credentials now works without error

[thomasyu888]

Hmm. Does it make sense to update to newer versions or is that a harder lift?

[rxu17]

So the problem is even the newest versions of the aws glue docker containers (glue 4.0) haven't been updated to use node 20 hence they all have node 16 / the glibc version 2.26 that the aws actions cannot accept because the aws actions use node 20 / glibc version >= 2.27.

The above would only be a temp. solution though. A more long term solution (until the above gets fixed) i was thinking of and mentioned in the discussion is by building Node.js statically so it doesn't matter what glibc version is used by the docker container. Not sure how viable this is yet so going to try it.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud