Upgrade sonar-maven-plugin 3.9.1.2184 -> 3.11.0.3922

[Picnic-Bot]

This PR contains the following updates:

Package	Type	Update	Change
sonar-maven-plugin (source)	build	minor	3.9.1.2184 -> 3.11.0.3922

---

Release Notes

SonarSource/sonar-scanner-maven (sonar-maven-plugin)

v3.11.0.3922

Compare Source

Release notes - Sonar Scanner for Maven - 3.11

Bug

MSONAR-205 Undesired behaviour when sonar.projectKey is specified in root pom or as user property

Documentation

MSONAR-203 Update license headers

Task

MSONAR-208 Migrate tests to JUnit 5

Improvement

MSONAR-202 Improve logging : log information about Maven options, Java version and the OS

MSONAR-204 "SonarQube version" is not displayed when communicating with SonarCloud

MSONAR-207 The scanner for Maven collects files outside of conventional sonar.sources

v3.10.0.2594

Compare Source

Release notes - Sonar Scanner for Maven - 3.10

New Feature

MSONAR-193 Set property `sonar.java.enablePreview` when Java's enablePreview feature is set

Task

MSONAR-184 Properly escape multi-valued properties if some paths contain comma

MSONAR-187 Upgrade github-action_release to v4

MSONAR-188 Stop leaking Maven classes in the scanner engine classloader

MSONAR-189 Add ITs with java 17

MSONAR-192 Run all tests nightly

MSONAR-195 Reduce the scope of the maven-compat dependency

MSONAR-198 Add Maven 4 tests to the pipeline

MSONAR-199 Use master build for peachee jobs

Improvement

MSONAR-190 Default sources to "src/main" instead of "src/main/java"

MSONAR-197 Maven Scanner relies on old slf4j version

---

• If you want to rebase/retry this PR, check this box

[Picnic-Bot]

Suggested commit message:

Upgrade sonar-maven-plugin 3.9.1.2184 -> 3.11.0.3922

See:
- https://github.com/SonarSource/sonar-scanner-maven/releases/tag/3.10.0.2594
- https://github.com/SonarSource/sonar-scanner-maven/releases/tag/3.11.0.3922
- https://github.com/SonarSource/sonar-scanner-maven/compare/3.9.1.2184...3.11.0.3922

[Picnic-Bot]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.