Re-introduce VERSION in @turnkey/http

[r-n-o]

Summary & Motivation

This re-introduces the changes from #186 and #187 after they were reverted in #190.

I'm very, very disappointed in Changesets, a tool we're using for releases. npm itself has plenty of lifecycle hooks to handle custom scripts pre and post version (see this). But these lifecycle hooks aren't called by changeset version! Wut. People are complaining about this...

• pnpm changeset version should invoke preversion & postversion npm hook scripts pnpm/pnpm#2911
• enable updating custom version files with changeset version changesets/changesets#1166
• Expect changesets to run NPM related hook functions changesets/changesets#1145

...but no responses from the maintainers.

I tried instrumenting preversion, prepublish, version, etc...nothing seems to work because changeset doesn't call any of these. In the end I settled for a custom "version" script. This has the advantage to be explicit but it's one more script to call during releases. The problem: what if we forget to call it when we publish new versions? For this I've got a CI check which should catch any oversight.

How I Tested These Changes

• Ran version script locally to make sure it works
• Broke things on purpose with this commit to trigger the CI check
  

Did you add a changeset?

Yes! ✅

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[emostov]

Nice - we can include running the pnpm version command in release instructions

[r-n-o]

Nice - we can include running the pnpm version command in release instructions

Yep! That's my next PR once this one is merged! 🙏