Apply Configured MySQL Connection Pool Settings

[STK0Cervanthes]

oh what a Cerv in the PR's? someone stop this man. full disclosure this PR text are my ramblings turned into a coherent PR by john Co Pilot.

Summary

The database pool settings were read from configuration but never applied to the MySQL connection string.

As a result, production silently used MySql.Data defaults instead of the configured pool size. This could cap the application at approximately 100 connections despite db_max_poolsize being configured as 500.

Changes

• Apply db_min_poolsize to MinimumPoolSize.
• Apply db_max_poolsize to MaximumPoolSize.
• Apply db_use_pooling to Pooling.
• Apply db_conn_reset to ConnectionReset.
• Add the pool settings to the sample appsettings.json. (this seems to be allready set in prod just not in the template i guess)
• Preserve MySql.Data defaults when older deployments omit these settings.

Configuration

Production should include:

{
  "Database": {
    "db_min_poolsize": 10,
    "db_max_poolsize": 500,
    "db_use_pooling": true,
    "db_conn_reset": true
  }
}

dotnet build ran without issues and warnings.

This PR is technically related to a general issue in DB pooling and possible exhaustion but focuses on adressing only the con pool config issue.

C# aint my strong sword but this server magic is feel free to critisize and call me names if i fucked up.