BE: fix presets vulnerabilities: use new version in docker image

To fix [vulnerability issue](https://security-tracker.debian.org/tracker/source-package/db5.3), use newer python image in [Dockerfile](https://gitlab.com/opengeoweb/backend-services/presets-backend/-/blob/main/Dockerfile). 

Update code to accomodate this new version

----
What has been done:
* Tried to use new debian version `bookworm`
  * No official python version with bookworm is available: https://hub.docker.com/_/python
  * So I tried to use `debian:bookworm` and install python in that image
  * This did **not** work as this image could not be scanned on AWS (see [this](https://eu-west-1.console.aws.amazon.com/ecr/repositories/private/568951685059/gitlab/pipeline-scan/image/sha256:4f1ab5d9e4d96bad163ef2b4c4f1add90da6b85f82ffffed58618070dade9a4f/details/?region=eu-west-1))
* Tried to use a newer python version with the same debian version
  * `python:3.10.6-slim-bullseye` instead of `python:3.9-slim-bullseye`. (During refinement it was agreed to use a newer version of python)
  * Additionally, tried to use a fixed version of the vulnerable package db5.3 which was released for `bookworm`
  * This still marked the package as vulnerable
 
**Conclusion:**
* Vulnerability is still marked as high, so the decision was made to whitelist the vulnerable package
* The new version of python will be kept (python 3.10 instead of 3.9)
* It seems now that the only way to fix this vulnerability is waiting until a python image with `bookworm` is released
* In the end, only this [MR](https://gitlab.com/opengeoweb/backend-services/presets-backend/-/merge_requests/49) has to be merged (with new python version). The 2nd MR mentioned was created to deploy the dev branch of the presets-be and pass the vulnerability scanning. A third MR (https://gitlab.com/KNMI/geoweb/geoweb-serverless-backend/-/merge_requests/332) can be cleaned up. This one was used to deploy the serverless BE in order to test the dev branch in a local FE.


---
How to test:
* You can test functionalities in local FE with the following `config.json`:
```
{
  "GW_AUTH_LOGIN_URL": "https://geoweb-dev.auth.eu-west-1.amazoncognito.com/oauth2/authorize?client_id={client_id}&response_type=code&scope=email+openid&redirect_uri={app_url}/code&state={state}&code_challenge={code_challenge}&code_challenge_method=S256",
  "GW_AUTH_LOGOUT_URL": "https://geoweb-dev.auth.eu-west-1.amazoncognito.com/logout?client_id={client_id}&logout_uri={app_url}/login",
  "GW_AUTH_TOKEN_URL": "https://non3m9kr27-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/infra/auth/token",
  "GW_AUTH_CLIENT_ID": "7lnismfj33ddrsdtss3qthglji",
  "GW_INFRA_BASE_URL": "https://non3m9kr27-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/infra",
  "GW_APP_URL": "http://localhost:5400",
  "GW_SW_BASE_URL": "https://co5iqnti4a-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/spaceweather",
  "GW_AIRMET_BASE_URL": "https://i2kc0llw1g-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/aviation",
  "GW_SIGMET_BASE_URL": "https://i2kc0llw1g-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/aviation",
  "GW_TAF_BASE_URL": "https://i2kc0llw1g-vpce-026bc1761b17f4f69.execute-api.eu-west-1.amazonaws.com/aviation",
  "GW_PRESET_BACKEND_URL": "https://gwpresetsbe-dev-2527-fix-vulnerabilities.geoweb.dev.knmi.cloud",
  "GW_INITIAL_PRESETS_FILENAME": "knmi.initialPresets.json", 
  "GW_SCREEN_PRESETS_FILENAME": "knmi.screenPresets.json",
  "GW_FEATURE_LAYER_SELECT": false,
  "GW_FEATURE_APP_TITLE": "KNMI GeoWeb",
  "GW_FEATURE_FORCE_AUTHENTICATION": true,
  "GW_FEATURE_MODULE_SPACE_WEATHER": true,
  "GW_FEATURE_MODULE_TAF": true,
  "GW_FEATURE_MODULE_SIGMET": true,
  "GW_FEATURE_MODULE_AIRMET": true,
  "GW_FEATURE_MENU_SATCOMP": true,
  "GW_FEATURE_MENU_FEEDBACK": true,
  "GW_FEATURE_MENU_INFO": false,
  "GW_FEATURE_MENU_VERSION": true
}
```

* Go to https://localhost/5400
* Open presets
* Test that functionalities remain the same

Story points: 5.0