chore: enable SQL checks in Sonar

[andrablaj]

Description

SQL checks in Sonar were disabled for this repo. As it contains mostly SQL code, re-enable SQL checks in Sonar.

Code review checklist

• Readable: Concise, well named, follows the style guide, documented if necessary.
• Documented: Configuration and user documentation on cht-docs
• Tested: Unit and/or e2e where appropriate
• Backwards compatible: Works with existing data and configuration or includes a migration. Any breaking changes documented in the release notes.

License

The software is provided under AGPL-3.0. Contributions to this project are accepted under the same license.

[njuguna-n]

This looks good. One question though, is it possible to run an analysis on existing code before merging this? The SQL code in this repo also makes use of Jinja templating and wondering if Sonar will handle this correctly. I have checked out this branch and run Sonar lint locally through the VSCode plugin no issues but just want to be sure Sonar Cloud will be the same.

[andrablaj]

I forked the repo last week and merged this commit on the fork, and Sonar didn't raise any issues, so in the state the code it's now, it should pass the quality gate. We can always tweak the Sonar rules in the future if we start getting false positives.

[njuguna-n]

🚀

[medic-ci]

🎉 This PR is included in version 1.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀