chore: regenerate clients for authzed/api@3270b08244f3e97e2a57a7ee2d9c649c88b861d3

[authzed-client-regen]

Regenerate clients for RoaringLookupResources

Upstream added authzed.api.materialize.v0.RoaringLookupResourcesService, a new
service (one RPC, ExperimentalRoaringLookupResources) that returns a
roaring64-encoded bitmap of the resource object IDs a subject has a given
permission on, for bulk export into a search index that supports
roaring-bitmap terms queries (e.g. OpenSearch's "value_type": "bitmap").
The proto tier for all seven languages (Go, Python, TypeScript, C#, Java,
Ruby, Rust) regenerated to pick up the new generated types/stubs under
materialize/v0/.

Only the TypeScript idiomatic client wires this into its public surface.
New public API:

• SpiceDBClient.experimentalRoaringLookupResources(params: RoaringLookupResourcesParams, consistency: Consistency): Promise<RoaringLookupResourcesResult>
• New exported types RoaringLookupResourcesParams and RoaringLookupResourcesResult ({ bitmap: Uint8Array, cardinality: bigint, revision: string }).
• SpiceDBProtoClient now exposes a fifth Connect client, materialize, alongside permissions/schema/watch/experimental.
• Every resource object ID must be a canonical decimal integer fitting in 44 bits, or the call fails FailedPreconditionError rather than returning a partial bitmap.
• Additive only, marked @experimental per DESIGN.md's naming convention. New example under examples/roaring_lookup_resources/ covers both the response mapping and the failure case (the test SpiceDB image doesn't implement this RPC yet, confirmed returning UNIMPLEMENTED).

The other six idiomatic clients (Go, Python, C#, Java, Ruby, Rust) only bump
.last-generation/CHANGELOG.md — no source changes. Each already doesn't
wrap the sibling materialize package (it's never surfaced its other
services either), so this is consistent prior behavior, not a regression.
Go's changelog additionally documents a real landmine: importing the new
materialize/v0 generated package alongside this module's own v1 package
panics at init from a duplicate proto file registration
(authzed/api/v1/core.proto) — a pre-existing bug in the generated gen/
files, out of scope to fix here, but worth a reviewer's awareness before
anyone tries to wire Go up next.

ddfa3b5 is a same-day, docs-only follow-up fixing an unresolved {@link bitmap} doc comment that broke mage apicompat; no API change.

Automated client regeneration.

• Upstream API pin: 3270b08244f3e97e2a57a7ee2d9c649c88b861d3
• Trigger: repository_dispatch / api_main_update
• Generation result: success
• Failed languages: none reported
• Resolved BSR commit: b7434c00783744819f061e14d2479b02 (from 3270b08244f3e97e2a57a7ee2d9c649c88b861d3)
• Run: https://github.com/authzed/spicedb-clients-prototype/actions/runs/35130536891

Reproduce locally, against the exact revision this ran on:

BUFTAG=b7434c00783744819f061e14d2479b02 mage gen:all