bot: bump SonarSource/sonarqube-scan-action from 5.2.0 to 6.0.0

[dependabot]

Bumps SonarSource/sonarqube-scan-action from 5.2.0 to 6.0.0.

Release notes

Sourced from SonarSource/sonarqube-scan-action's releases.

v6.0.0

BREAKING CHANGE!

In order to prevent command-line injection, the actions has been rewritten from Bash to JS, and the args input is now parsed differently. When updating to v6, you might have to update your workflow to change how arguments are quoted. For example, if you were previously passing:

- uses: SonarSource/sonarqube-scan-action@<action version>
  with:
    args: >
      -Dsonar.projectName="My Project"

you should now pass:

- uses: SonarSource/sonarqube-scan-action@<action version>
  with:
    args: >
      "-Dsonar.projectName=My Project"

For more args passing examples, please refer to the README file

What's Changed

• SQSCANGHA-106 Migrate from Bash to JS by @​jeremy-davis-sonarsource in SonarSource/sonarqube-scan-action#208

Full Changelog: SonarSource/sonarqube-scan-action@v5.3.1...v6.0.0

v5.3.1

OVERLOOKED BREAKING CHANGE!

In order to prevent command-line injection, the way to parse the args input has been changed, but this is possibly a breaking change regarding support of quotes.

For example, if you were previously passing:

- uses: SonarSource/sonarqube-scan-action@<action version>
  with:
    args: >
      -Dsonar.projectName="My Project"

you should now pass:

- uses: SonarSource/sonarqube-scan-action@<action version>
  with:
    args: >
      "-Dsonar.projectName=My Project"

Edit: We have now released v6 that more accurately reflect this breaking change.

What's Changed

... (truncated)

Commits

• fd88b7d SQSCANGHA-119 New Readme structure
• 27a157d SQSCANGHA-118 Update the README to document the breaking change for args parsing
• e327da8 NO-JIRA Add documentation for contribution
• ff001fd SQSCANGHA-107 Migrate install-build-wrapper
• a88c96d SQSCANGHA-107 Make room for install-build-wrapper action
• a642810 SQSCANGHA-112 SQSCANGHA-113 Fixes from review and keytool refactor
• 60aee70 NO-JIRA Disable fail fast on matrix jobs
• 502204e NO-JIRA Fix test assertion
• 0b794a0 SQSCANGHA-112 Delete legacy shell script
• ece10df SQSCANGHA-112 Extract installation step and other fixes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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)

[codara-ai-code-review]

Potential issues, bugs, and flaws that can introduce unwanted behavior.

1. Version Compatibility:
   /.github/workflows/sonarcloud.yml - Upgrading from version v5.2.0 to v6.0.0 of the SonarSource action without reviewing the release notes or migration guide can lead to incompatibilities or breaking changes. Ensure all features and configurations used in the pipeline are still supported in the new version.

Code suggestions and improvements for better exception handling, logic, standardization, and consistency.

1. Add a Comment About Version Update:
   /.github/workflows/sonarcloud.yml - Include a comment next to the version number change explaining the rationale for the update. This will help other developers understand the reasoning behind the upgrade and facilitate future maintenance.

   # Updated to v6.0.0 for new features and improvements, verify compatibility.

2. Handle Token Storage Securely:
   /.github/workflows/sonarcloud.yml - The use of secrets.SONAR_TOKEN is good practice. Ensure that there are clear instructions in your repository’s documentation about managing GitHub Secrets properly, as security measures surrounding tokens are critical.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ BASH	bash-exec	1		0	0	0.24s
✅ BASH	shellcheck	1		0	0	0.07s
✅ BASH	shfmt	1	0	0	0	0.01s
✅ COPYPASTE	jscpd	yes		no	no	1.3s
✅ MARKDOWN	markdownlint	2	0	0	0	0.55s
✅ MARKDOWN	markdown-link-check	3		0	0	3.62s
✅ MARKDOWN	markdown-table-formatter	3	0	0	0	0.18s
✅ REPOSITORY	checkov	yes		no	no	10.9s
✅ REPOSITORY	gitleaks	yes		no	no	0.06s
✅ REPOSITORY	git_diff	yes		no	no	0.0s
✅ REPOSITORY	grype	yes		no	no	25.16s
✅ REPOSITORY	syft	yes		no	no	1.06s
✅ REPOSITORY	trivy	yes		no	no	6.05s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.09s
✅ REPOSITORY	trufflehog	yes		no	no	2.14s

See detailed report in MegaLinter reports

[Klintrup]

@dependabot rebase

[dependabot]

Looks like SonarSource/sonarqube-scan-action is up-to-date now, so this is no longer needed.