fix(lambda-python): poetry bundling is broken after Aug 20 (#26823)

The Dockerfile that builds an executable container to run `poetry` in installs the latest version of `poetry` on a Python 3.7 Docker image.

Unfortunately `poetry 1.6.0`, released August 20, drops support for Python 3.7 which means that all poetry bundling jobs started failing on that date. `1.6.0` also does not work on Python 3.8, which I don't see mentioned in the change log, but our integration tests that use Python 3.8 are also broken.

Lock the poetry version back to `1.5.1` by using a version specifier so the command is not dependent on the date it is run.

This is the last version that supported both Python 3.7 and 3.8.

----

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

Author: rix0rrr

packages/@aws-cdk/aws-lambda-python-alpha/lib/Dockerfile

@@ -6,6 +6,7 @@ FROM $IMAGE
 ARG PIP_INDEX_URL
 ARG PIP_EXTRA_INDEX_URL
 ARG HTTPS_PROXY
+ARG POETRY_VERSION=1.5.1
 
 # Add virtualenv path
 ENV PATH="/usr/app/venv/bin:$PATH"
@@ -17,7 +18,7 @@ ENV PIP_CACHE_DIR=/tmp/pip-cache
 ENV POETRY_CACHE_DIR=/tmp/poetry-cache
 
 RUN \
-# create a new virtualenv for python to use 
+# create a new virtualenv for python to use
 # so that it isn't using root
     python -m venv /usr/app/venv && \
 # Create a new location for the pip cache
@@ -31,7 +32,7 @@ RUN \
 # Ensure all users can write to poetry cache
     chmod -R 777 /tmp/poetry-cache && \
 # pipenv 2022.4.8 is the last version with Python 3.6 support
-    pip install pipenv==2022.4.8 poetry && \
+    pip install pipenv==2022.4.8 poetry==$POETRY_VERSION && \
 # Ensure no temporary files remain in the caches
     rm -rf /tmp/pip-cache/* /tmp/poetry-cache/*