chore(deps): bump advanced-security/maven-dependency-submission-action from 3 to 4

[dependabot]

Bumps advanced-security/maven-dependency-submission-action from 3 to 4.

Release notes

Sourced from advanced-security/maven-dependency-submission-action's releases.

v4.0.0

Version 4.0.0 release:

• Breaking change, the name presented in the submission report now matches the current name of the repository maven-dependency-submission-action (previously it was moved from a repository called maven-dependency-tree-action)
• When running the GitHub Action the ref and sha are injected as inputs (with defaults to the current workflow values)
• Updated dependencies, specifically dependency-submission-toolkit that includes improvements to uploading of the snapshots and error handling around unhappy path scenarios
• CLI application options made compatible with the GitHub Actions inputs
• CLI applications made available as part of the release process and notes
• Project testing and releases - swapped jest out for vitest and added GitHub Actions release workflow

v3.0.3

• Fixes issue with POMs that set a non-default outputDirectory resulting is no dependency data being found and uploaded #48.

v3.0.2

What's Changed

• Make action GHES compatible by @​cnagadya in advanced-security/maven-dependency-submission-action#40

New Contributors

• @​cnagadya made their first contribution in advanced-security/maven-dependency-submission-action#40

Full Changelog: advanced-security/maven-dependency-submission-action@v3...v3.0.2

v3.0.1

• Updated to latest dependency snapshot library 1.2.10
• Fixed error in the cli tools that was incorrectly validating the branch specification #26
• Correctly injecting the additional maven command line options #28

Commits

• ed72a32 chore: Updating release files
• 33937f9 4.0.0
• 9300a13 Updating test time out so it can complete on a GitHub Actions runner
• bc9f3a7 Loosening test around lgged lines that change in versions of maven
• e5df479 Updating compiled dist files
• 6ed65ae Adding release workflow
• 8e6e39a Removing jest and replacing with vitest
• ed528f7 Updating dependency-submisssion-toolkit to 2.0.0
• f8fe527 Updating version number and adding release workflow
• eb1b04b Fixing installation issues on devcontainer
• 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)

[github-actions]

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

1. Register at Qodana Cloud and configure the action
2. Use GitHub Code Scanning with Qodana
3. Host Qodana report at GitHub Pages
4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2023.3.1
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions