fix(db): validate SSL certificate on production database connections

[sg-gs]

What

Both database SSL configs now validate the server certificate (rejectUnauthorized: true) instead of disabling verification:

• src/config/sequelize.js (used by sequelize-cli for migrations)
• src/app.module.ts (used by the running app, for both the main and drive database connections)

The CA is read from environment variables (base64-encoded PEM), decoded via ConfigService at runtime.

Why

The previous config used rejectUnauthorized: false in both places, disabling certificate verification and exposing the connections to MITM attacks. The main and drive databases are separate instances, each with its own CA, so each connection now validates against its own certificate.

⚠️ Requires new environment variables before deploying to production:

• DB_CA_CERT — base64-encoded PEM CA certificate for the main database
• DRIVE_DB_CA_CERT — base64-encoded PEM CA certificate for the drive database

[sg-gs]

It's still in draft @TamaraFinogina

[TamaraFinogina]

Yes, but only due to the missing variable, no?

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[sg-gs]

Draft means not ready for review, with independence of the reason haha @TamaraFinogina. In fact, it was not just a value missing. I discovered migrations and server's db connection using independent sequelize configs.

[sg-gs]

Now it's ready for review @TamaraFinogina. Tested it locally using OVH's certs.

[sg-gs]

Environment variables are already configured in production also ✅