chore: port Bash scripts to JS

[nschonni]

Description

• Took the original work from ci(update): port update.sh to nodejs #1368 and rebased it for the conflicts.
• Updated the code to reflect the Yarn changes.

Todo:

• Still needs to address the build-automation.mjs since the script no longer takes a version as a parameter
• Still needs to incorporate the "security" concept for the musl builds

Motivation and Context

Testing Details

Example Output(if appropriate)

Types of changes

• Documentation
• Version change (Update, remove or add more Node.js versions)
• Variant change (Update, remove or add more variants, or versions of variants)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Other (none of the above)

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING.md document.
• All new and existing tests passed.

[MikeMcC399]

It would be great to have a test suite to go along with this. At the moment we continually get surprised by the outcomes of automation, for instance when the Node.js publishing goes wrong and the data that docker-node relies on is in an inconsistent state.

This PR would also need documentation changes to match.

I realize that this is still just draft status, but wanted to share my thoughts anyway!