docs: publish consolidated docs using mkdocs

[thephez]

Issue being fixed or feature implemented

Given the changed project structure, it appears that docsify won't work in a monorepo format. Prior to having this monorepo, a number of its packages hosted documents on their own repository Github Pages sites (js-dapi-client, js-dash-sdk, js-dpp, and wallet-lib). These sites were built via docsify.

What was done?

I found MkDocs which accomplishes a similar purpose. While it doesn't directly support monorepos, I found it to be more flexible than docsify. This PR uses it, along with a GH action to publish an aggregated set of documentation for those 4 packages. Fortunately it works relatively well with no modification to the documentation source files.

How Has This Been Tested?

I experimented using a fork of this repo and deploying the resulting documentation on that repo's GH Pages site: https://thephez.github.io/platform/. There are a few broken links and malformed markdown in the existing files that will need to updated, but those changes would be a separate PR after this is mergedhave been made in PR #49 .

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone

[shumkov]

LGTM! 👍

[thephez]

@shumkov or @antouhou, this built successfully when merged and created the gh-pages branch (https://github.com/dashevo/platform/tree/gh-pages) necessary to MkDocs. IIRC, someone with access to the repo settings will still have to go in there and enable GitHub Pages before they will be published to https://dashevo.github.io/platform/.

Also, 000be71 should be integrated to the v0.22 branch.