chore: remove badge and master-detail-layout feature flags

[web-padawan]

Description

These components will become stable in 25.2 so let's remove feature flags (WC and FC already updated).
Slider will be also removed in WC beta1 but it also needs Flow component PR, so I'll update it separately.

Type of change

• Internal change

[ZheSun88]

seems we also need to remove this from flow
https://github.com/vaadin/flow/blob/main/flow-server/src/main/java/com/vaadin/experimental/FeatureFlags.java#L62
and https://github.com/vaadin/flow/blob/main/flow-server/src/main/java/com/vaadin/experimental/FlowComponentsFeatureFlagProvider.java

[web-padawan]

@ZheSun88 created vaadin/flow#24427 to remove MasterDetailLayout (Badge isn't listed there).

[github-actions]

Dependencies Report

• 🚫 Vulnerabilities:

  • Vulnerabilities in: pkg:maven/org.apache.tomcat.embed/tomcat-embed-core@11.0.21 [CVE-2026-43515, CVE-2026-43513, CVE-2026-43514, CVE-2026-42498, CVE-2026-41284, CVE-2026-43512, CVE-2026-41293, BIT-tomcat-2026-43515, BIT-tomcat-2026-43513, BIT-tomcat-2026-43514, BIT-tomcat-2026-42498, BIT-tomcat-2026-41284, BIT-tomcat-2026-43512, BIT-tomcat-2026-41293] (osv-bomber,osv-scan,owasp)
    · cpe:2.3:a:apache:tomcat::::::::
    ·
  • Vulnerabilities in: pkg:npm/js-cookie@3.0.5 [CVE-2026-46625] (osv-bomber,osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/org.apache.tomcat/tomcat@11.0.21 [BIT-tomcat-2026-43515, CVE-2026-43515, BIT-tomcat-2026-43513, CVE-2026-43513, BIT-tomcat-2026-43514, CVE-2026-43514, BIT-tomcat-2026-42498, CVE-2026-42498, BIT-tomcat-2026-41284, CVE-2026-41284, BIT-tomcat-2026-43512, CVE-2026-43512, BIT-tomcat-2026-41293, CVE-2026-41293] (osv-scan)
    ·
  • Vulnerabilities in: pkg:maven/org.apache.tomcat/tomcat-catalina@11.0.21 [BIT-tomcat-2026-43515, CVE-2026-43515, BIT-tomcat-2026-43513, CVE-2026-43513, BIT-tomcat-2026-43514, CVE-2026-43514, BIT-tomcat-2026-42498, CVE-2026-42498, BIT-tomcat-2026-41284, CVE-2026-41284, BIT-tomcat-2026-43512, CVE-2026-43512, BIT-tomcat-2026-41293, CVE-2026-41293] (osv-scan)
    ·

• 🟠 Known Vulnerabilities:

  • Vulnerabilities in: pkg:maven/me.friwi/jcef-api@jcef-ca49ada%2Bcef-135.0.20%2Bge7de5c3%2Bchromium-135.0.7049.85 [CVE-2024-21639, CVE-2024-21640, CVE-2024-9410] (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::::::::
    · cpe:2.3:a:ada:ada::::::::
  • Vulnerabilities in: pkg:maven/com.networknt/json-schema-validator@1.5.9 [CVE-2025-15104] (owasp)
    👌 FP: The CVE belongs to Nu Html Checker which produce a false positive on Networknt JSON Schema Validator due to the overlapping keyword or an overly broad CPE mapping rule.
    · cpe:2.3:a:validator:validator::::::::
  • Vulnerabilities in: pkg:maven/com.vaadin/vaadin-swing-kit-flow@3.0.1 [CVE-2021-33604] (owasp)
    👌 false report: this CVE is targeting Vaadin version prior 20, swing-kit-flow is using vaadin 24+ version, the related issue has been fixed.
    · cpe:2.3:a:vaadin:flow-server::::::::
    · cpe:2.3:a:vaadin:vaadin::::::::

• 📔 No Core License Issues

• 📔 No License Issues

• 🟠 Changes in 25.2-SNAPSHOT since V25.2.0-alpha8

  • 1 packages added (1 external, 0 vaadin)
  • 1 packages modified (1 external, 0 vaadin)
  • 659 packages same (424 external, 235 vaadin)

[Click for more Details]