Move the Hyde documentation files to this repo to be able to sync changes to master branch

[caendesilva]

Right now it's a bit tricky to deploy updates to the documentation that are timed to releases.

If the docs are updated to early I end up having documentation that has features that don't yet exist, if I do it after I may forget to update them.

Thinking a good or at least better way to solve this is to add a docs directory here, and propagate changes to the docs repo. Changes in the docs repo are also synced here. This introduces complexity since the docs repo is also synced to DocsCI. Here I am thinking that when running the CI building process, a job in the action downloads the latest documentation files.

[caendesilva]

Or better, once a release is published, then the docs get updated. While there is a delay of a few minutes (more if there are merge conflicts) it could be a better implementation.

Or, even even better if I (or someone who sees this) can design a workflow for it keeps the contents of the docs here in sync with a new "upcoming" branch of the docs, which can then be merged when a release is published (or just before)

[caendesilva]

Note to self: remember to add the docs directory to export-ignore

[caendesilva]

Think for now I may add a dev-docs directory here, and sync it to a dev branch on the docs repo. I can then trigger merge manually there.