New scan workflow + sonar project config file to enable sonarqube scans

[dandelany]

Per MGSS/AMMOS requirements, we need to use a combination of CodeQL + SonarQube for security scans moving forward, via GH actions. This will ultimately be implemented in all PlanDev repos & will replace the existing CodeQL scans.

This is affected by this nasa-scrub issue and contains a temporary workaround to avoid it, which we can easily remove later when fixed upstream.

JPL internal docs with details: https://wiki.jpl.nasa.gov/pages/viewpage.action?spaceKey=AmmosArch&title=Code+Vulnerability+Scanning+Set+Up+for+AMMOS+Open+Source+Software

See also: NASA-AMMOS/plandev-ui#1935

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

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