refactor(core): implement RoutedViewComponent

[sleidig]

to generalize loading of config from route data

as a basis for the new admin / setup UI

⚠️ mark as codo

[github-actions]

Deployed to https://pr-2062.aam-digital.net/

[TheSlimvReal]

Really good idea and nice to see how easy it was to implement this. This makes the difference between route components and panel components even smaller. That might be useful at one point.

[TheSlimvReal]

Can you explain a little why this is needed in general? What will change with the admin UI?

[sleidig]

Can you explain a little why this is needed in general? What will change with the admin UI?

In general, I've had the thought to make components usable in both dialog popups and main full-screen views. (Although here I realized that making the Dialog-based components generic is still some more work, so skipping this here for now)
In particular, with regards to the Admin UI, I wanted to keep the components to configure views and entities independent of router data because we might want to display these inside some kind of stepper for a guided setup process also.

As a bonus: Also easier to use in Storybook ;-)

[aam-digital-ci]

🎉 This PR is included in version 3.26.0-master.5 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[aam-digital-ci]

🎉 This PR is included in version 3.26.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀