Feature/refactor shared util layout

[mloeffle]

As agreed in one of our JFs, here is a suggestion to reduce the content of the Layout/Shared/Util folders.

• Layout got removed
• Util got cleaned up
• Shared got cleaned up

My thoughts about this were:

• Own folder: Everything with a specific content get into a folder to group components which make the most sense to be used together
• Shared: Components offering a blueprint that does get its content eg from Slots an can be used in every context
  • still in one folder so we have one place to look what is available
• compoments root:
  • components that cant be assigned with others to be combined in a dedicated folder
• Util
  • components that don't offer customiziation in each context and just get placed somewhere (eg UtilityPill, UtilityLogo, they get only one to very few props)
  • Disclaimer: I wanted these components to go into components root, but the linting then fails due to vue/multi-word-component-names so I wanted to open the conversation to change this

[m-borgmann]

This looks good for now. Just wanted to note here that we will have to see how well the Pagination can be adapted to multiple different contexts. If any issues arise in the future there might be a debate to move it to Shared, as it grows more complex.

[mloeffle]

Agree, we have to see how its going to work out.

[m-borgmann]

This (alongside LandingPage and NavigationPage) feels kinda weird. Putting them in a folder does make sense, but the naming "Frontend" is a little bland. Perhaps something like "PageProvider" would make it more clear what they do? 🤔 so they would be called -> PageProviderDetail, PageProviderLanding and PageProviderNavigation.

[mloeffle]

I understand what you mean, but sadly the logic on how the content is rendered requires them to start with Frontend since the component name is generated from the SW route like frontend.detail.page.