Builtin docs linter & utilities

[marcinjangrzybowski]

PR checklist:

• Test coverage for the proposed changes
• PR description contains example output from repl interaction or a snippet from unit test output
• Any changes that could be relevant to users have been recorded in the changelog

Additionally, please justify why you should or should not do the following:

• Confirm replay/back compat
• Benchmark regressions
• (For Kadena engineers) Run integration-tests against a Chainweb built with this version of Pact

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1206540398567844

[marcinjangrzybowski]

For now I prepared required glue code, and some basic example linting rules, to be able quickly implement actual rules once convention for our docs is decided by the team.
I am set up to meet with linda to learn what I can begin with.

Example markdown files with documentation where directly exported from notion documents.

[marcinjangrzybowski]

based on scraping of older docs, and results of linting of current md files,
it can also generate summary of builtin docs state:
docs-utils/docs-utils/generated/summary.md

[marcinjangrzybowski]

Also, I expect some of this code to be droped, once I talk to jose and got his thoughts on what should be the focus here.

[rsoeldner]

closing as core builtin docs are captured in #122