ci: kzb-33 add sonar build workflow

[oneanupam]

Description

Please include a short summary of the update made along with the context.

Checklist

• Self-review of the code is performed.
• Code has been fully tested and completely functional.

Type of Change

• break: Resolved a breaking change. This will increment the major version.
• feat: A new feature or enhancement added to the codebase. This will increment the minor version.
• fix: A bug fix or correction to resolve an issue. This will increment the patch version.
• chore: Other changes not directly affecting the code (e.g., documentation update). No version increment.

Reference

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/creating-a-pull-request-template-for-your-repository

[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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud