Containerless

[baabcantcode]

resolves #33 resolves #32

additionally using ts - temporarily removed tests since they were too much trouble to get them working with @actions/core, not sure why thats so resistant to input mocking. figure best bet is to mock nothing except fs for @actions/core and pass through the input object to things that would have normally called getCliArgs

still wondering why releasing is such a pain with GH actions. i'll also update test code to require failures so we dont get false positive test passing anymore

[baabcantcode]

ugh i need to readd the unit tests. should be easier now at least. those things were such a pain when everything was calling getCliArgs from inside their modules.

functional tests are more complete and can actually catch things with the new output data, but i really want to test the early failures that can happen in getCliArgs, and the errors that are thrown for bad download urls

[baabcantcode]

current plan: readd current jest tests add extended coverage with fast-check