Sync aws-lambda-nodejs-runtime-interface-client

Related issues:

- followup from https://github.com/aws/aws-lambda-base-images/issues/47#issuecomment-1321832240
- closes https://github.com/aws/aws-lambda-base-images/issues/38 and https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/issues/44
- helps address https://github.com/aws/aws-lambda-base-images/issues/59

---

> Great news!
>
> @jtuliani will you and the team update https://github.com/aws/aws-lambda-nodejs-runtime-interface-client to match the Node.js 18 release?
>
> Features described in the blog post, like ES Module support https://github.com/aws/aws-lambda-nodejs-runtime-interface-client/issues/44, do not work. This support is very important for custom docker containers.

> @jlarmstrongiv You're right that the public runtime interface client is not currently in sync with our Node 18 version. It is something we want to address. Can I suggest you file a separate issue for this, for tracking purposes and for others to weigh in with their feedback?

---

Syncing the [aws-lambda-nodejs-runtime-interface-client repository](https://github.com/aws/aws-lambda-nodejs-runtime-interface-client) with the current version released in amazon lambda nodejs base images will:
- avoid unexpected discrepancies between environments
- ensure ESModule support in custom docker containers
- allow testing and migrating lambda functions in the new Amazon Linux 2022 container