feat!: add commands from the ps-exec plugin to the core CLI

[k80bowman]

Summary

Adds the ps:copy, ps:exec, ps:forward, and ps:socks commands from the ps-exec plugin to the core CLI. This also includes adding the util functions from heroku-exec-util to the core CLI and migrating everything to work with TypeScript and @oclif/core v4. This PR also adds unit tests for the helper functions and the commands, something that did not previously exist.

Type of Change

Breaking Changes (major semver update)

• Add a ! after your change type to denote a change that breaks current behavior

Feature Additions (minor semver update)

• feat: Introduces a new feature to the codebase

Patch Updates (patch semver update)

• fix: Bug fix
• deps: Dependency upgrade
• revert: Revert a previous commit
• chore: Change that does not affect production code
• refactor: Refactoring existing code without changing behavior
• test: Add/update/remove tests

Testing

Notes:

In order to test these commands, you will need to use a test app with a dyno. In order to test ps:copy you will need a test app with a dyno that contains files. The internally-shared app heroku-demo-app works.

Steps:

1. Check out this branch and run npm i && npm run build
2. Run ./bin/run ps:copy test.js -a heroku-demo-app and verify that the test.js file has been downloaded
3. Run ./bin/run ps:exec -a heroku-demo-app and verify that you have successfully sshed into the dyno
4. Run ./bin/run ps:exec -a heroku-demo-app -- node -i and verify that the node -i command is run on the dyno. (You should get an error message about node not being available or recognized).
5. Run ./bin/run ps:forward 8080 -a heroku-demo-app and verify that it is successfully forwarding. Use ctrl+c to end the forwarding.
6. Run ./bin/run ps:socks -a heroku-demo-app and verify that the socks port has started. Use ctrl+c to end the forwarding.

Related Issues

GUS work item: W-17567656

[eablack]

some failing tests, but otherwise looks great!