Re-enable sonarqube for quality assessment

[wadoon]

Issue

As discussed in the kakey meetting, the current situation of the quality assessment tool is rather unsatisfying. This PR removes the current tools (pmd, checkstyle, qodana, codeql) in favor sonarqube (again).

Intended Change

Integration of sonarqube. Removal of the rest.

Type of pull request

• maintenance

Ensuring quality

• inspecting sonarqube
• trusting sonarqube

[wadoon]

@Drodt @WolframPfeifer

I added this branch to some of PR to test the analysis:

• Package structured reworked for sealed packages #3473
• Renovation of the TestCase generation #3388
• Exploiting JML Names in the Proof Tree #3022
• Create a JSON-RPC for KeY #3303

So we can investigate the difference analyses.

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

[WolframPfeifer]

I don't think that this PR matches our conclusion from the KaKeY. At least for spotless, I think we agreed that we want to keep it (can be read between the lines here https://git.key-project.org/key/key/-/wikis/KaKeY/KaKeY-2024-10-25).

Also, I think we agreed to remove Qodana, CodeQL, and PMD. But I am not sure (and did also not find anything in the logs) about a decision for Checkstyle and Sonarcloud ... Did I miss something?

[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