Add Code quality analysis to the repo.

[Tatsinnit]

Summary

This PR integrates CodeQL analysis into our CI/CD pipeline to enhance security scanning and code quality checks. CodeQL will automatically analyze our codebase for security vulnerabilities, performance issues, and maintainability concerns.

Changes in This PR 💡

• Added .github/workflows/codeql.yml to enable CodeQL scanning in GitHub Actions.
• Configured CodeQL to run on pull requests and main branches for continuous security monitoring.
• Set up language-specific analysis based on our repository's tech stack.
• Enabled automatic security alerts for detected vulnerabilities.

Why This Is Important 🚓

• Detects potential security flaws early (e.g., SQL injection, XSS, buffer overflows).
• Prevents vulnerable code from being merged by annotating issues in PRs.
• Improves overall code quality and performance using advanced data flow analysis.
• Seamless integration with GitHub Advanced Security for better visibility.

How It Works ⛑️

• Runs on every PR and main branch push to catch issues before merging.
• Reports findings directly in the PR, allowing developers to address them proactively.

Next Steps 🥇

• Lets monitor and triage CodeQL security alerts.
• Adjust custom queries if needed for project-specific vulnerabilities.
• Review and address any critical issues flagged after merging this PR.

Thanks heaps

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[jveski]

Thanks @Tatsinnit!