fix: npm script awareness, TS fixes, test env refactors

[kanadgupta]

🧰 Changes

• We're seeing an issue where TS builds fail if they include this version of rdme in their deps... so this PR installs keyv and it evidently fixes it¹ 🤷🏽 31c6700
• npm and yarn use an env var called npm_lifecycle_event to indicate the current npm run script. This feels like a good place to not have our GitHub Action onboarding prompts run 🙅🏽 09cdbf2
• Small refactors to (hopefully) guarantee that our testbed env logic won't conflict with any env vars in the wild 🦁 6fbfedf
  • All internal testing env values (i.e. for testing CI or testing GitHub Action creation) are prefixed with TEST_RDME_
  • Renamed our NODE_ENV for our tests from test to rdme-test
  • As part of the above, I created a little isTest helper to check whether we're running tests
• Made small cleanups in our testbed 🧹
  • Optimized our Prettier check to only check Markdown files since ESLint already covers JS/TS files 6a1c232
  • Small cleanup in our test console output b320a97

🧬 QA & Testing

I npm link'd this PR to our Metrics API codebase and ran npm run build in that codebase and confirmed that:

• The TS error no longer exists
• Chained npm scripts like the one below work as they previously did:

If our test bed passes, we should be good to go 🥳

Footnotes

1. See: https://stackoverflow.com/q/74141618 ↩

[erunion]

that lifecycle env var is a great find.