Fix TypeScript protobuf resolution

[stephanos]

Summary

• bump github.com/temporalio/features to the commit from Bump protobufjs pnpm override 7.5.1 → ^8.7.1 features#892
• declare protobufjs as a direct dependency of generated TypeScript workers
• move the configured TypeScript SDK baseline from 1.22.0 to 1.23.0 and synchronize nested worker dependencies
• ensure generated protobuf types and the Temporal TypeScript SDK 1.23 converter resolve the same protobufjs module instance

Why

The TypeScript kitchen-sink job began resolving SDK 1.23.0, whose protobuf JSON converter requires protobufjs 8. The old features override forced protobufjs 7.5.1, causing Cannot find module 'protobufjs/ext/protojson'. After lifting that override, OMES generated code still resolved protobufjs from the parent source package while the SDK converter resolved it from the generated pnpm package; the two module instances have distinct Type classes and failed with type must be a Type.

Declaring protobufjs in the generated package keeps both sides on the same pnpm module instance. Aligning OMES's configured TypeScript worker baseline with 1.23.0 avoids exercising that protobufjs 8 package with the incompatible 1.22 SDK, and committing the synchronized worker manifests keeps the dependency freshness check clean.

Merge order

1. Bump protobufjs pnpm override 7.5.1 → ^8.7.1 features#892
2. this PR
3. Run kitchen sink SDK tests in isolated namespaces #462

Testing

• SDK=typescript go test -v -race ./loadgen -run TestKitchenSink -count=1
• go test -race ./internal/workerctl
• npm --prefix workers/typescript run typecheck
• npm --prefix workers/typescript run lint-ci
• mise run sync-sdk (verified idempotent)
• git diff --check

[stephanos]

Fails without this.

[stephanos]

Closed in favor of #475