Improve local development/testing workflow

[MetricMike]

Is your feature request related to a problem? Please describe.

Kinda stuck in error-driven development - make a change, commit, wait for Github Actions, guess at fix for whatever build is failing. Developing this plugin could be much easier!

Describe the solution you'd like

(split these into other tickets)

• Examples/workflow for a more robust debugger like BashDB
• Examples/workflow for making a change, and testing locally (point to git repo on disk instead of github? BATS?)
• Setup codespaces so a collaborator can just . on this page, apply fix, and publish a PR in ~10 minutes (arbitrary number) with nothing but a browser
• Document dependencies because it is so annoying to use something like long flags on uname and then have macos blow up in GithubActions (see: https://github.com/MetricMike/asdf-awscli/actions/runs/4794362683/jobs/8527665463#step:3:45 and docs: track full list of asdf dependencies asdf-vm/asdf#1435)
• Implement caching/workflow reuse to speed up GithubActions? Feature request: Caching asdf-vm/actions#235 Use Existing Setup Actions When Available asdf-vm/actions#442
• Hook into ASDF BATS to ensure we're keeping up with upstream's requirements/best practices? feat: CI tooling for asdf plugins which checks for asdf core banned_commands asdf-vm/actions#514 Improve testing with plugin repositories asdf-vm/asdf#1512
  • also ASDF Plugin Standard Library asdf-vm/asdf#1318 https://github.com/bash-bastion and
• Implement all scripts (the helper/dependencies ones are what I'm most excited about) feat: implement latest-stable from GH releases with fallback asdf-vm/asdf-plugin-template#61 https://asdf-vm.com/plugins/create.html#scripts-overview
• Implement benchmarking ala asdf shims adding too much time to use them in a shell prompt asdf-vm/asdf#290 http://stratus3d.com/blog/2022/08/11/asdf-performance/
• enforce semantic commits before GH Actions yell at me