Initialize Sonarcloud for test coverage and code quality reports

[nikomakela]

HCRC-186.

1. Initialize a Sonarcloud properties file to trigger code quality and test coverage scanning and reporting. The Sonarcloud project can be found in https://sonarcloud.io/project/overview?id=city-of-helsinki_react-helsinki-headless-cms.
2. Start using the city of Helsinki common workflows for CI and stable releases. NOTE: Canary release not yet supported by the common templates. Templates are available in https://github.com/City-of-Helsinki/.github/blob/main/.github/workflows/.

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

[nikomakela]

I expect that we need to transfer the NPM project to some other organisation in order to get the common publish template to work.

[nikomakela]

I think we should also setup a release please process for this repo. Sure it isn't mandatory to be done in this PR, but it would make this repo more consistent with other.

Release please would handle

1. the version numbering
2. git tag creation
3. writing the changelog

What do you think @terovirtanen and @karisal-anders ?

[karisal-anders]

.js files could be included, there aren't many of them

[karisal-anders]

The src/tests doesn't seem to be a test directory, it only has apolloConfig.tsx and hideConsoleMessages.tsx. Maybe the directory could be renamed to something else to make it clearer as to what it is. Because of this src/tests doesn't seem to be useful to include here.

[karisal-anders]

Left some comments. Please take a look at them.

[karisal-anders]

I think we should also setup a release please process for this repo. Sure it isn't mandatory to be done in this PR, but it would make this repo more consistent with other.

Release please would handle

1. the version numbering
2. git tag creation
3. writing the changelog

What do you think @terovirtanen and @karisal-anders ?

I'm slightly eager to get the SonarCloud coverage & reporting into main branch, so because of that I think it'd be better to split that to another PR.

[terovirtanen]

I think we should also setup a release please process for this repo. Sure it isn't mandatory to be done in this PR, but it would make this repo more consistent with other.

Release please would handle

1. the version numbering
2. git tag creation
3. writing the changelog

What do you think @terovirtanen and @karisal-anders ?

I agree. release-please example can be found from https://github.com/City-of-Helsinki/react-helsinki-notification-manager/blob/0fcf09a90576c7669b0edfe08c36429f6a506772/.github/workflows/release-please.yml

[nikomakela]

I can merge this so we get the sonar cloud running, as @karisal-anders suggested. I'll start to setup release-please next @terovirtanen .

[sonarqubecloud]

Quality Gate failed

Failed conditions
4 Security Hotspots
28.4% Duplication on New Code (required ≤ 3%)
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE