fix: avoid encoding MariaDB connection properties

[aaron-congo]

Description

• fixes Undesired URL encoding of connection property #1222
• before these changes, we encoded the property values passed to the buildUrl function. This function is only actually called when using a MariaDB data source. We do not encode MySQL or Postgres driver/datasource connections, and we do not encode MariaDB driver connections. Encoding the property values for MariaDB changes the intended values for the properties and can cause connection failures (see the linked issue above). I believe this encoding was originally intended to be used with MySQL and/or Postgres, but did not end up being used in those scenarios and isn't required for them either. This PR removes the call to encode the property values.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

1. Register at Qodana Cloud and configure the action
2. Use GitHub Code Scanning with Qodana
3. Host Qodana report at GitHub Pages
4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions