BE: Configure Presets BE with Cognito part 1

# Test:

- Check out https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/1583 and start `nx serve knmi-geoweb`
- Make sure the frontend is started over http://localhost:4200
- Make sure you are on connect
- Go to the layermanager, check if presets are listed.

# Description

A new endpoint `viewpresetauth` was added for authenticated preset requests. The existing `viewpreset` is left unchanged. The `viewpresetauth` endpoint is useful to have, because it will give a 401 unauthorized error if no access token is provided or if something is misconfigured.

You can check https://gwpresetsbe-dev-check-auth.geoweb.dev.knmi.cloud/viewpreset and https://gwpresetsbe-dev-check-auth.geoweb.dev.knmi.cloud/viewpresetauth

By using the command `curl -k --location  https://gwpresetsbe-dev-check-auth.geoweb.dev.knmi.cloud/viewpresetauth' --header 'Authorization: Bearer ....'` you can sign in from the command line.

- Nginx https, ssl and generation of self signed certs can be switched off by setting the environment variable`PRESETS_ENABLE_SSL=FALSE`. The http port can be set with `NGINX_PORT_HTTP`. Nginx should not use https by itself when it is deployed behind an AWS elastic load balancer and should only listen to HTTP.
- Nginx communicates with cognito to get user information based on the OAuth2 Bearer token send with the `viewpresetauth` request. The userinfo endpoint of the identity provider can be set via the `OAUTH2_USERINFO` environment variable.
- For CORS, nginx needs to know the domain of the frontend. This needs to be set with the `FRONTEND_APP_URL` environment variable.
- Nginx sets the "Geoweb-Username" header for the flask presets backend
- An endpoint is deployed at https://gwpresetsbe-dev-check-auth.geoweb.dev.knmi.cloud (only accessible via connect). 

The cognito userinfo endpoint and the location of the frontend are configured from CI/CD via the OAUTH2_USERINFO and FRONTEND_APP_URL variables. These have been set for dev, tst, acc and prd.

# Solved Issues

- Nginx in the ECS cluster will talk via the KNMI squid proxy with gitlab or cognito. Squid has some quirks, therefore only TLSv1.2 and TLSv1.3 can be used. (Only TLSv1.3 icm gitlab). 
- The EC2 load balancer uses by default the http/2 protocol. When running http/2, it changes all HTTP headers which are forwarded to nginx to lowercase. Disabling http/2 solves this issue. Nginx expect the authorization header to be `Authorization` with strict casing (not `authorization`)
- Because of CORS, the frontend and the backend needs to match domains. Therefore FRONTEND_APP_URL must be configured, which is the location of the GeoWeb Frontend.
- In the ECS cluster, nginx needs to be accessed via HTTP. It should be started without the self signed HTTPS certificate. It is now possible to switch this off and run nginx over http. For HTTPS, the Elastic Load Balancer will do the HTTPS offloading and handle the SSL certificates. This can be switched off in nginx by setting the environment variable `PRESETS_ENABLE_SSL=FALSE` and setting the `NGINX_PORT_HTTP` environment variable.

Closes https://gitlab.com/opengeoweb/opengeoweb/-/issues/2180

# MR for presets-backend (this ticket)
- https://gitlab.com/opengeoweb/backend-services/presets-backend/-/merge_requests/16

# Related MR for testing purposes
- For presets-backend deployment: Then https://gitlab.com/KNMI/geoweb/backend-services/deploy-presets-backend/-/merge_requests/17
- For knmi-geoweb: https://gitlab.com/opengeoweb/opengeoweb/-/merge_requests/1583

Story points: 5.0