feat!: Remove AWS SDK V2 Dependency

[texastony]

Issue #, if available: #1100, #922, #865, #1178, #1177

Description of changes:
In CodeBuild Builds:

1. Always specify the exact Node version
2. Name files after the Node Version
3. Stop testing NodeJS 12 & 14
4. Start testing NodeJS 20
5. Use Node 18 for compliance

BREAKING CHANGE:
The AWS Encryption SDK for JavaScript:

• requires the AWS SDK for JavaScript V3's kms-client (if using the KMS Keyring).
• no longer requires the AWS SDK V2
• no longer tests against nor supports NodeJS 12 or 14.

Note: @seebees I had to merge #1177 and #1178 to get CodeBuild to pass.
I think the new package-lock only supports Node >= 16,
so I needed to drop the Node 14 tests.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Check any applicable:

• Were any files moved? Moving files changes their URL, which breaks all hyperlinks to the files.

[texastony]

I do not know why, but the CB testVectorsNodejs20 completes npm run verdaccio-publish and then just hangs until the CB request times out...

It does not run verdaccio-node-decrypt or anything else.

Huh... it's hanging on my local as well...

The question then is if it's learna or verdaccio that is hanging...

Huh... running the commands in util/local_verdaccio_publish with Node20 did not cause a hang...

So something is up with the actual JS in util/local_verdaccio_publish.

Fudge.

Update: I resolved this by setting a time out for the lerna process and having it call process.exit() on close.

[seebees]

LGTM

[seebees]

My guess is that this is required because you have added a timeout.
That timeout is likely implemented with setTimeout.
This means when this is executed there is an event in the background.

[texastony]

Hmm... it was hanging before I added the timeout.
But I guess I could check to see if just exit fixes the hang, with out the time out.