Added building and pushing docker image for the lambda-extension

[AlexanderWert]

Closes #195

[ghost]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-06-01T06:54:22.945+0000

• Duration: 6 min 18 sec

Test stats 🧪

Test	Results
Failed	0
Passed	200
Skipped	4
Total	204

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[v1v]

LGTM, minor comments, only one question regarding the docker image for multiarch, as far as I see, the docker image will be different for x86 and arm. Is that the intended? I'm happy about this anyway, but wanted to double check if for any reasons we wanted a docker image multi-arch based instead, since it will require some other implementation

[v1v]

I'm not much familiar with WORKERS but CI is the default env variable if it helps

[AlexanderWert]

I copied this logic from the Java agent's push_docker.sh

[AlexanderWert]

I see, the docker image will be different for x86 and arm. Is that the intended?

Yes it is intended. Depending on the AWS Lambda architecture the users would use the corresponding image to get the extension with the correct arch.