feat: add engine docs to docs.ooni.org

[DecFox]

Checklist

• I have read the contribution guidelines
• reference issue for this pull request:
• if you changed anything related to how experiments work and you need to reflect these changes in the ooni/spec repository, please link to the related ooni/spec pull request:
• if you changed code inside an experiment, make sure you bump its version number

Description

This diff introduces workflow to show docs in ooni/probe-cli on docs.ooni.org

[hellais]

Wherever it says mydocs it should instead say probe

[hellais]

It's a good start, but it's missing critical pieces to make it mergeable.

Basically I would do a find . -type f -name "*.md" in the root of probe-cli and then figure out where they should live on docs.ooni.org and come up with reasonable slugs and titles for each of them.

You can ignore readmes that are very redundant, things like this one: https://github.com/ooni/probe-cli/blob/master/internal/cmd/README.md, which have basically not relevant content in them. However things like this: https://github.com/ooni/probe-cli/blob/master/internal/tutorial/dslx/chapter01/README.md should be included in docs.ooni.org and placed in the right place (eg. /probe-engine/dslx/tutorials/chapter-1)

Moreover the directory of the docs should not be mydocs, but rather should be probe or probe-engine

[DecFox]

We are only pushing the following docs to docs.ooni.org for now: docs/design/*, docs/releasing.md, pkg/oonimkall/* and README.md.

[DecFox]

Thanks for the review! I have pushed the desired changes. As proposed, we have renamed the content directory for ooni/probe-cli docs to be probe-engine here: https://github.com/ooni/probe-cli/pull/1634/files#diff-4dfe935b4852393622c2b414783d1d11e1a868fd8485709124d90208fa61ec8bR26

[hellais]

This looks good to me. We should also add probe-engine to the sidebar, but that can be done directly in the ooni/docs repo.