chore(cm): refactor CM

[joshuaellis]

What does it do?

Overall, this PR absolutely destroys the CM. But, it shakes off loads of tech debt, makes data transformations clearer and isolated to one place. It also introduces new public APIs for users

• refactors the layouts for the edit/list view & introduces useDocumentLayout hook
• introduces useDocument hook
• introduces useDocumentActions hook
• introduces useDocumentRBAC hook (not public)
• introduces Form, InputRenderer components & associated hooks
• refactors the CM to be more driven by domains ✨
• documents how the CM works from a high level
• Adds tabs in the EditView & the new header component
• removes reducers for the edit view & list view

What does it not do

• Document actions in the ListView do not work incl. bulk actions
• You can't view created documents, you can only create them
• Document actions in the EditView do not work
• i18n does not work all the code to inject the plugin in the admin panel has been temporarily removed
• RBAC on components is most likely broken, this will be tested later

Related issue(s)/PR(s)

• resolves CONTENT-1813
• resolves CONTENT-2016
• resolves CONTENT-2021

[joshuaellis]

I need to add more documentation & fix the test suite and probs add a few more bits. But overall, I think this PR is good to be shared for this first bits.

[jhoward1994]

Hey, here are a few things I noticed that you might not be aware of from a functional test of the app

• CTB

  • Unable to update or delete content types {"error":"The \"path\" argument must be of type string. Received undefined"}

• CM

  • Pagination doesn't work. e.g. entries per page filter does not work
  • Accessing single types

I'm wondering, as this PR changes so much how much of the broken behaviour are you aware of? & where should I focus my review (in terms of code and functional testing)?

[joshuaellis]

I'd keep it to code review, we can functional test the feature to be honest (it's going into a feat branch) ✨