Restructure monorepo to be simpler

[caendesilva]

The way the monorepo works now is rather complex. Part of this is the multistage splitting process, and the way releases work. I tried keeping a changelog manually but find it hard to make the propagated releases relevant. I like the feature GitHub has to automatically generate release notes from pull requests, so I'm going to try out requiring pull requests for development instead of pushing directly to the master branch. This would then allow us to go back to handling patch releases in the readonly repositories. Since during the beta stage minor releases function partly as major ones, those should always be synced. Meaning that if Hyde get's a minor release, so must Framework, and vice versa.

• Require pull requests to contribute to the develop repo
• Remove intermediate jobs in the monorepo splitter to push directly to the readonly repos
• Remove the mirror branches
• Remove or decouple the keep a change changelog parser

[caendesilva]

Okay so small internal changes, like updating workflows, styles, and things like that should not be in changelog and could be pushed to master, and since I'm the only one who normally can push to master I'll just make a note to not push changes directly.

[caendesilva]

Remove or decouple the keep a change changelog parser

Not sure what do to about that so closing this issue for now and I'll handle the changelog later