docs: pseudo-automated new reference markdown file (#747)

As requested by @TC-MO, I've pseudo-automated the generation of the
reference file that people see on our docs!

I will add in more documentation on how to alter this later (more
specifically handling new commands added to the CLI), as its a manual
mapping of commands (unfortunately couldn't do it fully automated due to
some commands having different positions across the categories)

There probably is a better way to handle this in the future, I just did
the speedy way for now. Ideally, we'd use oclif's systems to load all
commands, store some specific field on each command class and rely on
that to map commands around, but even then we'll need to handle custom
ordering which might make it janky. To be determined

---------

Co-authored-by: Michał Olender <[email protected]>

Author: vladfrangu

.github/workflows/check.yaml

@@ -8,9 +8,6 @@ on:
         branches: [master, renovate/**]
     pull_request:
         branches: [master]
-    # A release via GitHub releases will deploy a latest version
-    release:
-        types: [published]
 
 jobs:
     build_and_test:
@@ -51,6 +48,9 @@ jobs:
                   APIFY_CLI_DISABLE_TELEMETRY: 1
               run: yarn test
 
+            - name: Ensure the reference documentation builds
+              run: yarn update-docs
+
     test_python_support:
         name: Test Python template support
         strategy:

.gitignore

@@ -23,3 +23,5 @@ package.tgz
 test/tmp
 oclif.manifest.json
 tmp
+
+scripts/temporary-reference.md