feat: setup npm publish workflow

[bcho]

This pull request introduces a new GitHub Actions workflow for publishing npm SDKs, updates the Bun worker SDK to use published dependencies, and bumps the TypeScript SDK to a new alpha version. It also updates the package-lock.json for the TypeScript SDK, marking many dependencies as peer dependencies for better compatibility.

Release automation:

• Added a new workflow .github/workflows/release-npm-sdks.yaml to automate publishing of the TypeScript and Bun worker SDKs to npm on GitHub release events. This workflow supports both npm and Bun, selects the proper npm dist-tag, and ensures only matching tags trigger the publish step.

SDK dependency and version updates:

• Updated @absurd-sqlite/bun-worker to version 0.2.0-alpha.1, changed its dependency on @absurd-sqlite/sdk from a local file reference to the published ~0.2.0-alpha.3 version, and fixed the description casing. [1] [2]
• Bumped @absurd-sqlite/sdk (TypeScript SDK) version to 0.2.0-alpha.3 in both package.json and package-lock.json.

Dependency management improvements:

• Updated sdks/typescript/package-lock.json to mark many dependencies as "peer": true, improving compatibility and reducing duplication in consumer projects. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25]

These changes streamline the release process, improve dependency management, and prepare both SDKs for wider consumption via npm.