watch bt releases on npm, update local bt version on update

[Cedric / ViaDézo1er (viadezo1er)]

Run with a daily cron job or manually.

Regenerate pnpm-lock.yaml once the bt binaries have been pushed to npm to fix CI.

Depends on braintrustdata/bt#208.

[Luca Forstner (lforst)]

This is not what we want. Updates should be manual as a minor in bt is a minor in sdk, and a major in bt, is a major in sdk.

[Luca Forstner (lforst)]

This should not be a .cjs file I think. In general, let's follow https://github.com/getsentry/sentry-cli/blob/master/scripts/install.js or https://blog.sentry.io/publishing-binaries-on-npm/ to the tee. The logs are very intentional there and we should log similar things to ensure people are not confused when installing the package and things fail.

I also have an example repo on how this should look like: https://github.com/lforst/npm-binary-example

[Cedric / ViaDézo1er (viadezo1er)]

We'll stick with manual version update for now.

[Cedric / ViaDézo1er (viadezo1er)]

Forgot we need to change the package.json to expose the bt binaries so we still need this PR.