New matching RPC: Check if version exists in TaskQueue

[Shivs11]

What changed?

• Added a new RPC method, scoped to matching only, which shall check if a specific version exists in the userData of a task queue.

Why?

• Currently, versioning has several places in history which call the method GetTaskQueueUserData to validate if a version exists in a task queue or not.
• However, with this going in very soon, one of the biggest changes put forward by it is the fact that a task queue's userData could go on to become big (if a task queue was part of a large number of versions). The main reason for this is because we keep an entry for versions that are deleted inside the task-queue's user data so that we can ensure read-after-write consistencies.
• Thus, to prevent large number of bytes flowing across the wire, it's best to just make this new RPC that does the check in matching and only sends a boolean across.

How did you test it?

• built
• run locally and tested manually
• covered by existing tests
• added new unit test(s)
• added new functional test(s)

Potential risks

• No risk honestly I think this is an optimization

---

Note

Introduces a matching RPC to check if a task queue belongs to a deployment version, wires it through proto, gRPC, clients, engine, quotas, and tests, and updates worker versioning to use it.

• API/Protobuf:
  • Add CheckTaskQueueVersionMembershipRequest/Response messages in api/matchingservice/v1/request_response.proto and generated Go files.
  • Add CheckTaskQueueVersionMembership method to MatchingService in service.proto and generated gRPC stubs.
• Server:
  • Implement handler Handler.CheckTaskQueueVersionMembership forwarding to engine.
  • Implement engine method matchingEngineImpl.CheckTaskQueueVersionMembership to read user data and return membership via worker_versioning.HasDeploymentVersion.
  • Include new RPC in rate-limiting quotas and logtags switch.
• Clients/Mocks:
  • Add client methods in generated client_gen.go, metric_client_gen.go, and retryable_client_gen.go.
  • Update gRPC client/server interfaces and register handler; add mocks in matchingservicemock.
• Worker Versioning:
  • Replace GetTaskQueueUserData check with CheckTaskQueueVersionMembership in detector.
• Tests:
  • Add functional test TestCheckTaskQueueVersionMembership validating false-before/true-after worker registration.

^{Written by Cursor Bugbot for commit ff2ea79. This will update automatically on new commits. Configure here.}

[Shivs11]

Technically, we don't need this (right now) since all the version presence checks for a task queue go through the workflow task queue type. However, I just wanted to be consistent with other matching API's since those that accept task-queue also accept the type. Moreover, we could have a future use-case of involving the activity task queue type of a task queue.

[ShahabT]

looks good otherwise

[ShahabT]

we're trying to move away from this proto as much as possible because it mixes multiple levels of TQs. In this case the API is only relevant to normal TQs, so just a string field is enough.