[Shubham8287]

Description of Changes

Based on #6376.

Adds TypeScript receiver bindings and outbox declarations for intermodule reducer calls.

It can be reviewed through commits:

1. Generate TypeScript receiver bindings with reducer handles, argument types, signature hashes, and dependency-specific identity types.
2. Wire receiver bindings into CLI generation and configured dependencies.
3. Add typed outbox declarations, generated shorthand, and onResult callbacks.
4. Map outbox columns to receiver parameters using .param({ name }) and make outboxes insert-only while preserving existing table APIs.
5. Add end-to-end smoke tests covering TypeScript and Rust senders and receivers, callbacks, receiver updates, and two dependencies with identical type names.

Proposal drfits:

• TypeScript sugar accepts only { name }, rather than { accessor, name }. The key passed to schema({...}) defines the accessor, matching regular TypeScript tables.
• Without an explicit name, the sugar uses the outbox table's accessor name (case converted) as the canonical name rather than defaulting to <reducer>Outbox.

API and ABI breaking changes

NA

Rollback safety impact

n/a

Expected complexity level and risk

Testing

unit tests and smoketests.

[cloutiertyler]

I'm okay to have this merge. The one thing I have concerns with is:

export const PingDetails = __t.object("game_world.PingDetails", {   // ← sender's name baked in
  labels: __t.array(__t.string()),
  owner: __t.identity(),
});

game_world I don't think should belong here. I think rather it should belong here:

export const PingDetails = __t.object("PingDetails", {              // ← same as the source
  labels: __t.array(__t.string()),
  owner: __t.identity(),
});
export type PingDetails = __Infer<typeof PingDetails>;

const __receiverModule: unique symbol = globalThis.Symbol() as typeof __receiverModule;
// The scope is given once, where the dependency is attached. remoteModule records
// the named types reachable from these params, and the sender registers them
// as game_world.PingDetails.
export default __remoteModule("game_world", {
  "receivePing": { /* unchanged */ },
}, __receiverModule);

I'm having Claude prototype this in a PR into this PR, but I don't think that should necessarily block this from merging (it is not hard to fix later, because we can just change codegen). See #6414 for what I'm talking about.