Review yarn vs npm vs others

[cloverich]

While adding github actions I ran into some conflicts with yarn. Not a big deal, but as suggested here, I'm most definitely using yarn because it was good years ago and npm was (very) bad. If npm is fine now, going back to it is one less dependency in setup and in CI.

• Review NPM setup
• Update any CI scripts (remove yarn)
• Carefully review the build and packaging steps, esp any rebuild or pruning

Could make sense to pair this with #118 (especially if touching the packagers)

[cloverich]

Read up a bit; npm will be a bit slower, but actually (correctly) fails to convert the proejct as is because of a couple of dependency conflicts (#159 ). Probably yarn will be the same. Ultimately this isn't blocking the rest of the feature work, so going to defer to next next sprint.