chore: Adjust server-less tooling for the new AWS Lambda "provided" run-times

[zatlodan]

What this PR does:

The "old" go1.x runtime is being deprecated.

Changes the CMD server-less build tooling to be compatible with the "new" AWS lambda run-times by default.

The "new" GoLang compatible AWS Lambda run-times expect an executable with the name bootstrap to be provided.
The handler configuration is ignored when using the "new" runtime.

See https://aws.amazon.com/blogs/compute/migrating-aws-lambda-functions-from-the-go1-x-runtime-to-the-custom-runtime-on-amazon-linux-2/ for more info.

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[CLAassistant]

All committers have signed the CLA.

[mapno]

LGMT. Can you add a changelog entry specifying what's being deprecated? Thanks!

[zatlodan]

LGMT. Can you add a changelog entry specifying what's being deprecated? Thanks!

Thank you, and sorry for the late response.

I've added a changelog entry.
Since this change only affects the build tooling, I didn't mark it as a breaking change,
although it might require adjustments for users relying on the previous build process.

Please let me know if any further adjustments are needed.

[github-actions]

This PR has been automatically marked as stale because it has not had any activity in the past 60 days.
The next time this stale check runs, the stale label will be removed if there is new activity. This pull request will be closed in 15 days if there is no new activity.
Please apply keepalive label to exempt this Pull Request.

[mapno]

I'd like to be a bit more explicit with the migration.

[zatlodan]

I'd like to be a bit more explicit with the migration.

I agree, it is better to be more explicit here.
I was initially not sure if I should mark it as a breaking change, as I am not used to writing change-logs.