fix: remove support for Node.JS 10.x

[kozlove-aws]

Problem

Node.js 10 is not supported anymore since April 10, 2021
We need to update it with newer library.

Solution

Replaced nodejs10 with nodejs14 in Docker file for lambda layer.
Also was changed to take amazonlinux from public.ecr for avoiding limit hit.

Testing

Was build image and deployed on local account.
Was verified that lambda layer is using nodejs12.x, nodejs14.x

---

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

[ddneilson]

Looks like Node 10 references here that should also be updated

• aws-rfdk/integ/package.json

  Line 110 in 8a55f32

  "node": ">= 10.13.0 <13 || >=13.7.0"

• aws-rfdk/packages/aws-rfdk/package.json

  Line 210 in 8a55f32

  "node": ">= 10.13.0 <13 || >=13.7.0"

• aws-rfdk/tools/pkglint/lib/rules.ts

  Line 632 in 8a55f32

  expectJSON(this.name, pkg, 'engines.node', '>= 10.13.0 <13 || >=13.7.0');

• aws-rfdk/tools/cdk-build-tools/package.json

  Line 73 in 8a55f32

  "node": ">= 10.13.0 <13 || >=13.7.0"

[horsmand]

Looks good, I only found one spot where we're referencing node 10 instead of node 12 in a message that pkglint prints out. I'm also wondering if we should be running npx yarn install so it can update the yarn.lock file. I see this line in there:

"@types/node" "^10.17.60"

[horsmand]

Suggested change

	message: `packages must support node version 10 and up, but ${atTypesNode} is declared`,
	message: `packages must support node version 12 and up, but ${atTypesNode} is declared`,

[kozlove-aws]

Good catch. yarn.lock is updated now.

[horsmand]

Did you include your changes in that most recent push? I don't see this rule or the yarn.lock updated.

[kozlove-aws]

You are right. Forgot to add files to commit.

[horsmand]

This looks good, I don't see anything that needs updating, but it seems you have a conflict in your yarn.lock so you'll need to rebase your changes and push them. I'll approve after that.

[jericht]

Looks good!

I only see the one reference to "@types/node@^10.17.60" that @horsmand mentioned in our yarn.lock file and it looks like it's a dependency of @aws-cdk/cloudformation-diff. We can force it to resolve to @types/node@12.x.x by adding an entry in the resolutions in the root package.json:

  "resolutions": {
    // ...
    "**/@aws-cdk/cloudformation-diff/**/@types/node": "^12.8.3"
  },

These are just the typings though, so not really necessary. I checked out @aws-cdk/cloudformation-diff, changed it to depend on "@types/node": "^12.18.3", then built and tested it and it succeeded, so I think it's safe to assume it's not relying on things that are incompatible between Node 10 and 12.