chore(deps): bump org.sonarsource.scanner.maven:sonar-maven-plugin from 3.9.1.2184 to 3.10.0.2594

[dependabot]

Bumps org.sonarsource.scanner.maven:sonar-maven-plugin from 3.9.1.2184 to 3.10.0.2594.

Release notes

Sourced from org.sonarsource.scanner.maven:sonar-maven-plugin's releases.

3.10.0.2594

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

Commits

• 07989ce Bump parent pom version to 68.0.0.247 (#186)
• 672a13c Update dependencies (#184)
• 35e9fac MSONAR-195 reduce the scope of maven-compact dependency (#183)
• eee75bf Add Java 11 Build pipeline
• 4fcd62a MSONAR-198 Add Maven 4 tests to the pipeline
• dbb6e9a Fix quality flaw: improve method detection regex
• 6ee5f98 Bump maven-shade plugin in tests
• c58de56 Use Java 17 for Build
• 0c896cc Update develop.md with Invoker Tests debugging instruction (#180)
• 2791f1b MSONAR-188 Remove explicit classloader masks and rely on the default Embedded...
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a eclipse-che member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.