chore: move away from oclif
This PR moves us off of oclif and all into yargs (/ open up a semi-easier migration path for other modules if we need to swap again in the future).
I've also been testing this out in both bun and node, so far it just works with any runtime and should be super easy to pack into an executable (to be determined if bun or node)
Biggest issue is the completely different help command, as right now it is rendered entirely by yargs. Advantage is we now have a much easier time building out the help messages ourselves, customization out the wazoo + easier (?) / more flexible generation of the docs reference page.
TODO:
- [x] finalize the migration to the current system
- [x] Try to implement a new help system or replicate oclif's
- [x] implement check for update hook
- [x] figure out testing in vitest (cucumber should work with miniscule changes)
Closes #735
move away from oclif, you mean?
brain = mush, yes