Update cloud-api protos to v0.14.0

[chndler]

What was changed

Bumped temporalio/cloud-api protos from v0.14.0 to v0.14.0 via git subtree.

Why?

Keep cloud-api in sync.

Checklist

1. Closes

2. How was this tested:

   • cargo check -p temporalio-client and cargo check -p temporalio-sdk-core-c-bridge both compile cleanly (only the expected 2 deprecation warnings on the upstream-deprecated RPCs)
   • cargo test -p temporalio-client --lib -- verify — all 5 verify_all_*_service_methods_implemented tests pass, including verify_all_cloud_service_methods_implemented which confirms ALL_IMPLEMENTED_CLOUD_SERVICE_RPCS exactly matches the proto definition (no drift)

3. Any docs updates needed?

---

Note

Medium Risk
Updates a large set of upstream protobuf definitions and the generated/forwarded client RPC surface, which can cause subtle compatibility issues for Cloud Ops consumers despite being mostly additive.

Overview
Bumps the vendored api_cloud_upstream protos/docs to v0.14.0, adding new Cloud Ops surfaces and versioned field changes.

This introduces Custom Roles support end-to-end: new CloudService RPCs (GetCustomRoles, GetCustomRole, CreateCustomRole, UpdateCustomRole, DeleteCustomRole), corresponding request/response messages, and new identity messages (CustomRole, CustomRoleSpec) plus AccountAccess.custom_roles.

Namespace protos are extended with replication/fairness constructs (ReplicaSpec/Replica, FairnessSpec, disable_passive_poller_forwarding) and deprecate older HA region RPCs/fields (AddNamespaceRegion/DeleteNamespaceRegion, NamespaceSpec.regions, Namespace.region_status). The Rust gRPC trait proxy impls are updated to #[allow(deprecated)] so deprecated upstream RPCs remain callable without breaking builds, and the C bridge RPC dispatcher is extended to route the new Custom Role calls.

^{Reviewed by Cursor Bugbot for commit 0c9d5d6. Bugbot is set up for automated code reviews on this repo. Configure here.}