TypeScript SDK: Rename address to connection ID

[gefjon]

Description of Changes

Typescript SDK companion to Rename Address to ConnectionId.

Re-generate the WS API schema bindings, rename address.ts, replace all instances of the word "address." All mechanical. Diff is artificially large because this PR is also the first time we've re-run spacetime generate since the new subscription API landed in public, which means there's a bunch of new WS messages in the client API folder. We don't use them, pending @cloutiertyler 's PR.

Note that this PR does not change the behavior where the SDK generates its connection ID locally, and passes it to the /database/subscribe endpoint. This can be changed in a follow-up.

API

• This is an API breaking change to the SDK

Address is now called ConnectionId.

Requires SpacetimeDB PRs

clockworklabs/SpacetimeDB#2220

[changeset-bot]

⚠️ No Changeset found

Latest commit: 460479e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/@clockworklabs/spacetimedb-sdk@133

commit: 460479e

[jsdt]

This looks right to me.

[gefjon]

While merging master into this PR, detected a bug in the Timestamp #114 impl: somehow that PR merged with the wrong field name in timestamp.ts. It should be __timestamp_micros_since_unix_epoch__, but it had been written as __timestamp_micros_since_unix_epoch (without the trailing double underscores). I've included the fix here.

[cloutiertyler]

I am force overriding the tests. I was in a meeting with Phoebe and this is because of a weird code gen merging order in SpacetimeDB. It is a known issue.