#217 Use full path from strapi `Router` content type

[radoslavzeman]

The aim of this PR is to propose a solution for routing of strapi content types (other than Pages), that should live on some specific urls, e.g. /o-nas/novinky/[slug]. This solution replaces our other solutions (map, translations, Navikronos), and uses normal strapi content type to store the routes. It also tries to use dynamic rewrites using middleware.ts instead of static rewrites defined in next.config.js.

This PR contains:

• create new content type "Router" that will contain all paths for other content types
• add GeneralContextProvider that fetches the router
• create dynamic rewrites in middleware - this is the tricky part that should be more discussed

Notes:

• only articles are added now - TODO other content types
• using the name Router is maybe not what we want
• I didn't spend too much time examining Next.js middlewares in general and the performance of this solution.
• I didn't test what happens if we use SSR and we would change the relation in Router, or the path of the page selected in router - this is the trickiest part - how we should propagate the changes

[github-actions[bot]]

Test build pipeline info :rocket:
Changes in the code and tag info:
:arrow_right: Changes in strapi: true
:arrow_right: Changes in next: true
We are going to build :ship:

:soon: strapi
:soon: next
:partying_face: Bratiska-cli successfully built an image from path: strapi/