chore: make hybrid dev module a provided dependency

[mcollovati]

vaadin-dev-bundle requires vaadin-hybrid-dev-bundle only to extract the hybrid
package-lock.json file. It necessary to have the hybrid bundle module as a
project dependency, to make sure modules are executed in the correct order by
maven reactor. However, the scope of the hybrid dependency must be provided
to prevent the flow maven plugin to find its stats.json in classpath and
then refusing to create a new dev bundle.

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/org.springframework/[email protected] [CVE-2024-38820] (osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/org.springframework/[email protected] [CVE-2024-38820] (owasp)
    · cpe:2.3:a:vmware:spring_framework::::::::
  • Vulnerabilities in: pkg:maven/org.springframework.security/[email protected] [CVE-2024-38821] (owasp)
    · cpe:2.3:a:org.springframework.security:spring-security-web:6.3.3:::::::*
  • Vulnerabilities in: pkg:maven/org.springframework/[email protected] [CVE-2024-38820] (owasp)
    · cpe:2.3:a:vmware:spring_framework::::::::
  • Vulnerabilities in: pkg:maven/org.springframework/[email protected] [CVE-2024-38819, CVE-2024-38820] (owasp)
    · cpe:2.3:a:org.springframework:spring-webmvc:6.1.13:::::::*
    · cpe:2.3:a:vmware:spring_framework::::::::
  • Vulnerabilities in: pkg:maven/org.springframework/[email protected] [CVE-2024-38820] (owasp)
    · cpe:2.3:a:vmware:spring_framework::::::::

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:npm/[email protected] [CVE-2024-34394, CVE-2024-34393] (osv-scan)
    👌 This is coming from the tools, @cyclonedx/cyclonedx, we have used for sbom module, FP for us.
    ·
  • Vulnerabilities in: pkg:maven/com.fasterxml.jackson.core/[email protected] [CVE-2023-35116] (owasp)
    👌 Not a valid CVE report based on the vendor analysis and research
    · cpe:2.3:a:fasterxml:jackson-databind::::::::
  • Vulnerabilities in: pkg:maven/me.friwi/jcef-api@jcef-af53d63%2Bcef-104.4.23%2Bg46ae630%2Bchromium-104.0.5112.102 [CVE-2024-21639, CVE-2024-21640] (owasp)
    👌 Wait for the update from the jcefmaven community. Meanwhile the swing-kit is supposed to be used with fixed websites and not to browse the internet, we have a check for that, so the only possible attacker would be the same person that created the swing application, aka our customer devs. so this vulnerability is not classified by us as critical issue
    · cpe:2.3:a:chromiumembedded:chromium_embedded_framework::::::::

• 📔 No License Issues

• 🟠 Changes in 24.6-SNAPSHOT since V24.6.0.alpha1

  • 31 packages removed (31 external, 0 vaadin)
  • 1 packages added (1 external, 0 vaadin)
  • 6 packages modified (6 external, 0 vaadin)
  • 1023 packages same (798 external, 225 vaadin)

[Click for more Details]

[mshabarov]

Is it a breaking change that requires this dependency to be added into hybrid projects?

[mcollovati]

Nope, that dependency is used only for platform build