feat(frontend): support autoforwarding through headers (#7681)

<!-- 1-2 line summary of WHAT changed technically:
- Always link the relevant projects GitHub issue, unless it is a minor
bugfix
- Good: "Modified FailoverDomain mapper to allow null ActiveClusterName
#320"
- Bad: "added nil check" -->
**What changed?**

add client feature flag support on server to enable autoforwarding

ref #7707

For ordering,
Payload > Header > default Eventual consistency level

* IDL update to support serialization in proto
* modified cluster redirection wrapper to honor consistency level from
feature flags

<!-- Your goal is to provide all the required context for a future
maintainer
to understand the reasons for making this change (see
https://cbea.ms/git-commit/#why-not-how).
How did this work previously (and what was wrong with it)? What has
changed, and why did you solve it
this way?
- Good: "Active-active domains have independent cluster attributes per
region. Previously,
modifying cluster attributes required spedifying the default
ActiveClusterName which
updates the global domain default. This prevents operators from updating
regional
configurations without affecting the primary cluster designation. This
change allows
  attribute updates to be independent of active cluster selection."
- Bad: "Improves domain handling" -->
**Why?**

Allows client workers to poll and process tasks from all regions. This
is particularly useful when a test infra started a test container that's
trying to process tasks during the test.

Before: you'll need to ensure the test container is started in region
that's connected to domain's active cluster
Now: all test containers can be auto forwarded to active cluster if they
provide the `client-feature-flag` header with auto forwarding enabled

<!-- Include specific test commands and setup. Please include the exact
commands such that
another maintainer or contributor can reproduce the test steps taken. 
- e.g Unit test commands with exact invocation
`go test -v ./common/types/mapper/proto -run TestFailoverDomainRequest`
- For integration tests include setup steps and test commands
Example: "Started local server with `./cadence start`, then ran `make
test_e2e`"
- For local simulation testing include setup steps for the server and
how you ran the tests
- Good: Full commands that reviewers can copy-paste to verify
- Bad: "Tested locally" or "Added tests" -->
**How did you test it?**

Unit Test
(WIP) Testing xdc clusters with cadence-samples to do xdc processing

<!-- If there are risks that the release engineer should know about
document them here.
For example:
- Has an API/IDL been modified? Is it backwards/forwards compatible? If
not, what are the repecussions?
- Has a schema change been introduced? Is it possible to roll back?
- Has a feature flag been re-used for a new purpose? 
- Is there a potential performance concern? Is the change modifying core
task processing logic?
- If truly N/A, you can mark it as such -->
**Potential risks**
The header is passed by clients. If they pass it wrong, inactive workers
will start processing workflows unexpectedly.

<!-- If this PR completes a user facing feature or changes functionality
add release notes here.
Your release notes should allow a user and the release engineer to
understand the changes with little context.
Always ensure that the description contains a link to the relevant
GitHub issue. -->
**Release notes**
added new field in structured `client-feature-flag` header to allow
users to set autoforwarding

<!-- Consider whether this change requires documentation updates in the
Cadence-Docs repo
- If yes: mention what needs updating (or link to docs PR in
cadence-docs repo)
- If in doubt, add a note about potential doc needs
- Only mark N/A if you're certain no docs are affected -->
**Documentation Changes**
N/A

---

## Reviewer Validation

**PR Description Quality** (check these before reviewing code):

- [ ] **"What changed"** provides a clear 1-2 line summary
  - [ ] Project Issue is linked
- [ ] **"Why"** explains the full motivation with sufficient context
- [ ] **Testing is documented:**
- [ ] Unit test commands are included (with exact `go test` invocation)
- [ ] Integration test setup/commands included (if integration tests
were run)
  - [ ] Canary testing details included (if canary was mentioned)
- [ ] **Potential risks** section is thoughtfully filled out (or
legitimately N/A)
- [ ] **Release notes** included if this completes a user-facing feature
- [ ] **Documentation** needs are addressed (or noted if uncertain)

---------

Signed-off-by: Shijie Sheng <liouvetren@gmail.com>

Author: shijiesheng

service/frontend/templates/clusterredirection.tmpl

@@ -70,7 +70,7 @@ func (handler *clusterRedirectionHandler) {{$method.Declaration}} {
 	var (
 		apiName = "{{$method.Name}}"
 		cluster string
-		requestedConsistencyLevel types.QueryConsistencyLevel = types.QueryConsistencyLevelEventual
+		requestedConsistencyLevel types.QueryConsistencyLevel = getRequestedConsistencyLevelFromContext(ctx)
 	)
 
 	{{- if has $method.Name $readAPIsWithStrongConsistency}}

service/frontend/wrappers/clusterredirection/api_generated.go

@@ -0,0 +1,22 @@
+package clusterredirection
+
+import (
+	"context"
+
+	"go.uber.org/yarpc"
+
+	"github.com/uber/cadence/common/client"
+	"github.com/uber/cadence/common/types"
+)
+
+func getRequestedConsistencyLevelFromContext(ctx context.Context) types.QueryConsistencyLevel {
+	call := yarpc.CallFromContext(ctx)
+	if call == nil {
+		return types.QueryConsistencyLevelEventual
+	}
+	featureFlags := client.GetFeatureFlagsFromHeader(call)
+	if featureFlags.AutoforwardingEnabled {
+		return types.QueryConsistencyLevelStrong
+	}
+	return types.QueryConsistencyLevelEventual
+}