chore: automate devcenter documentation updates

[k80bowman]

This PR completes the github action for updating our devcenter CLI commands documentation. Once we are sure this works, I will add it to our deploy workflows.

Notes

• There is a problem with all but one of the v5 plugins where the oclif readme command does not add the link to the code for each command in the CLI repo. This should be resolved when we release v9 of the CLI, so we have decided to leave it for now.
• This adds listings for the plugins:install, plugins:uninstall, and version commands that were not previously included.

Testing

Before pushing the new documentation to devcenter

• Check the artifact in this workflow run and validate that it contains the correct commands.

[justinwilaby]

LGTM

[eablack]

LGTM. couple questions just verifying things. but yeah, great work!

[eablack]

Somewhat significant jump in oclif/core but I don't see much in the changelog that we should be worried about. I noticed 2.16 was released literally yesterday (doesn't even show up in the changelog yet, heh). I think you had described to me something that the oclif team fixed that you asked about. Is that the update with 2.16?

[k80bowman]

Yes. They released a fix for us that allows for hidden aliases. We need it for the v9 release as well, so this was really helpful.

[eablack]

At the end of this it runs devcenter push /tmp/heroku-cli-commands.md.. were you able to test that this works by running this on your local machine (and doing gem install devcenter)?

[k80bowman]

That is my next step. I just wanted someone else to look over all of this first before running that script.