Release v4.221.0

Stage can now run an application as a published, permanent app for real users, and collect their feedback in the running app.

Added

• Published hosting mode (Stage:Mode=Published): Stage serves only the application, without Scalar, OpenAPI, the Workbench, the read-model browser or the specification and model-loading routes, and refuses to start unless forwarded identity from AuthProxy is on and limited to trusted proxy addresses. (part of #917)
• A published application keeps its data in MongoDB through Chronicle, in an event store named app-<published name> that survives restarts, redeploys and new versions. (part of #917)
• Versioned application packages: Stage exports a publishable package from a model, and a published container loads its application from such a package. (#918)
• In-app feedback through Cratis Showrunner Notes: a Notes button in the top bar and in the header of slice-owned dialogs, with the screen, slices and picked component as context, sent to the collecting host when Notes is configured for the published application. (#919)
• The frontend runtime exposes the application context (module, feature, slice, screen and dialogs) and a map from the running application back to the model, so feedback names the elements it is about. (#919)

Changed

• Generated applications now pin Cratis Arc 22.166.1, Chronicle 19.125.1, Fundamentals 7.33.1, Cratis.Specifications 5.2.3, @cratis/components 4.40.0 and @cratis/showrunner.notes / @cratis/showrunner.notes.react 1.0.0, alongside the latest releases of their other packages.
• Generated specifications keep their fully qualified test names under Cratis.Specifications 5.2.
• Stage itself runs on the same framework releases, with the bundled Chronicle kernel at 19.125.1 and Cratis.Showrunner.Notes 1.14.0.