Add branch name filter in cicd pipeline, update Python version, switch from psycopg2-binary to psycopg2, change executor in cicd pipeline

We want the cicd pipeline not to build a new image when the branch that kicks the PR is named doc-*, which means that only the documentation was updated.
We also need the Python version in the Dockerfile to be updated to 3.12.0b3-alpine, as suggested by Snyk (see #677)
We want to use psycopg2 instead psycopg2-binary, as the latter should not be used in production.
We need to change the executor used in the cicd pipeline, as the one currently configured for some reason creates a Geek Zone backend image with an older version of Python, which makes Snyk fail the pipeline.

Description

We are adding a step in the cicd pipeline with a conditional statement that will make it stop running if the branch that kicked it is named doc-*. However, the pipeline will show success, which is what we need to pass the PR checks.
We also updated Python version from 3.10.10-alpine to 3.12.0b3-alpine. This change needs some other changes in the Python files, without which the tests will fail (see a long list of recently failed cicd pipelines).
We switched from psycopg2-binary to psycopg2, which in turn needed a couple of dependencies to be added in the Dockerfile to work.
We switched from "machine" executor to "docker" executor.

Related Issue

resolves #674 resolves #681

Motivation and Context

The change is needed because at the moment any PR started from a branch named doc-* will not pass the cicd check. This is because the current cicd configuration makes the pipeline not run at all in such a scenario, thus the required cicd check will fail. Updating the Python version is needed to pass the Snyk checks, while all the modifications in the Python files are needed to pass the tests. Two packages were needed to switch from psycopg2-binary to psycopg2, which is not meant to be used in production. The executor configured for the cicd pipeline caused Snyk to fail the image.

How Has This Been Tested?

The logic that prevents the cicd pipeline to build a new image when only documentation is updated was tested in this cicd pipeline: https://app.circleci.com/pipelines/github/GeekZoneHQ/web/1972/workflows/58936093-d33c-4774-a133-cc0a0684a05a All the other changes were tested in the cicd pipeline, as shown in the passed check.

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

GeekZoneHQ / web