Release camunda-modeler v5.25.0

What's inside?

FEAT: show link to field documentation in the properties panel (bpmn-io/form-js#1201)
FIX: button labels properly evaluate expressions (bpmn-io/form-js#1181)
FIX: ensure group paths are properly registered on add (bpmn-io/form-js#1173)

To be done before the code freeze.

[x] inform QA about the release and its details so they can prepare for testing
[x] get in touch with the team (PM, UX and Engineering side), to clarify what topics will be included in the Release and their priority. Use this information to start preparing a concept for the blog post (see below) and release info (see below)
- [ ] (optional) if possible, already create feature branch to update Release Info following our guidelines

To be done after code freeze to prepare and test the release.

[x] make sure changes in upstream libraries are merged and released
- bpmn-js, dmn-js, *-properties-panel, *-moddle, camunda-bpmn-js, form-js, ...
[x] make sure potential new engine versions are available and marked correctly (alpha/stable)
[x] make sure dependencies to upstream libraries are updated and can be installed (rm -rf node_modules && npm i && npm run all works)
[x] verify develop is up to date with main: git checkout main && git pull && git checkout develop && git merge main
[x] close all issues which are solved by dependency updates
[x] ensure that the modeler is free of major security vulnerabilities via npm audit
[x] smoke test to verify all diagrams can be created
[x] update Release Info
- [ ] create a draft following our guidelines and based on priorities which were aligned with the team (PM, UX, and Engineering side)
- [ ] create PR to merge the draft into develop. Assign to PM, UX and Engineering for review
[x] update CHANGELOG
[x] compile a list of blog worthy changes as input to release blog
[x] merge to main: git checkout main && git merge develop
[x] create release candidate (npm run release:rc -- [preminor|premajor|prerelease]), cf. release schema
- [x] wait for release build to create the artifacts
[x] execute integration test on released artifacts
- [x] Works on Linux
- [x] Works on Mac
- [x] Works on Windows
[x] notify QA about the release so they can test it

To be done to build the release after release testing completed.

[x] create release (npm run release), cf. release schema
- [x] wait for release build to create the artifacts

To be done once the release is built.

[x] publish release on Github Releases
[x] update Camunda Modeler screenshots (and potentially text content) in the docs by running screenshots workflow. Download artifacts and create PRs for:
- [x] camunda-docs-static
- [x] camunda-docs-manual
- [x] camunda-docs
[x] provide content to the release presentation and notice
[x] trigger downloads page update via marketing request form
[x] add new version to update server releases
[x] (optional) update supported environments page

To be done once release is publicly announced on release day.

[x] publish release via update server (push to live)
[x] announce the release via the Camunda internal #c8-release-announcements channel
[x] communicate closed support related issues to #ask-support
[x] close current milestone