chore: bump remaining 24.6 versions to 24.7

[taefi]

Upgrading react-components to 24.7 alpha needs a release from components, and will be done separately.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.61%. Comparing base (33efa09) to head (5b0527e).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2968   +/-   ##
=======================================
  Coverage   92.61%   92.61%           
=======================================
  Files          84       84           
  Lines        3156     3156           
  Branches      769      769           
=======================================
  Hits         2923     2923           
  Misses        181      181           
  Partials       52       52           

Flag	Coverage Δ
unittests	92.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[cromoteca]

I'd avoid making those changes in package.json files, as they should come from the automatic PRs.

[taefi]

I'd avoid making those changes in package.json files, as they should come from the automatic PRs.

I've reverted the unnecessary components version upgrades, and only upgraded some weirdly not-upgraded deps such as @vaadin/bundles (some of the are upgraded, some are not). The rest, I'm updating them intentionally, to make sure, some tests are not passing just by pointing to old version accidentally. Also, there are projects such as endpoints-maven-engine or tests/spring/native that are not being upgraded automatically, as they're not included in the root pom.xml.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud