feat: custom runtimes, optional VPC, python 3.11

[emileten]

A large PR with several breaking changes.

• ⚠️ breaking change. bootstrapper runtime made configurable. This necessitated to 'merge' the database and bootstrapper into a single construct to avoid JSII issues. With this, all apps have their runtime configurable.

• ⚠️ breaking change. switched to Function and fromDockerBuild for lambda functions, because the state of PythonFunction makes it very hard to add flexible configurability. Now, users can override any of the lambda Function parameters they want ( code, but also memory, time out...).

• made VPC optional for lambdas

• harmonized pgstac to 0.7.10 in default runtimes.

• harmonized python to 3.11 in default runtimes.

[vincentsarago]

This looks good to me.

We should make sure to document this part to explain how basic dockerfile should look

# IMPORTANT: Use the same version of python for the asset building and lambda deployment
FROM public.ecr.aws/lambda/python:3.10

WORKDIR /tmp
RUN python -m pip install pip -U

# Install application dependency 
COPY runtime/requirements.txt requirements.txt
RUN python -m pip install -r requirements.txt "mangum>=0.14,<0.15" -t /asset

# Copy handler and custom code
COPY runtime/src/*.py /asset/

[sharkinsspatial]

@emileten We should also consider adding dockerignore file with cdk.out included at a minimum to reduce overall context size now that you are using Docker builds for all Lambdas.

[emileten]

I addressed comments ; I'll see if I can fit that into eoAPI and after confirming it works I'll fix conflicts and merge.

[emileten]

@vincentsarago FYI in the meanwhile (this took me forever 🙄) I did these changes (I updated the description):

• -> python 3.11 (so I'll close your other PR)
• made VPC optional for lambdas (this allows for a cheap, low-security deployment without a nat gateway)
• to make the bootstrapper runtime customizable I had to merge the database and the boostrapper construct together. This is a breaking change but unfortunately necessary: the way things were designed, with the two constructs being interdependent, but separated, was preventing me from making the bootstrapper options configurable (was encountering some JSII issues).

This is tested in deployment and good to go, about to merge!