Implement the library package on the landing page

[TomasEng]

We need to implement the @studio/content-library package on the dashboard and make it possible to navigate to it.

• Create a landing page component that implements the content library
• Establish routing for the new page

[standeren]

As a result from a discussion during team workshop we suggest that we should implement a home level above our current dashboard. This home level should include the following underlying pages, which will also act as menu-elements in the header:

1. resources
2. org-datamodels
3. org-library
4. app-dashboard --> which will be the current dashboard but without resources and org-datamodels

These menu-elements should vary if the the logged in user is not a part of any organization. Then the user should be passed directly to the app-dashboard.

When the user is in the context of self, but he/she belongs to at least one organization, the user should be asked to choose an organization to view the library for. In the future we can consider to implement a list of possible orgs to choose from in the main view when the user open the org-library and has context self. A solution is also to force the context to be the first available org.
If the user only belongs to a single org, we can also consider forcing the context to be the only available org of the user clicks on the library while being in self context.

[TomasEng]

The routing issue described by the above comment will be addressed in #14576.