fix: ensure that IDL submodules and go modules are synced (#1473)

chore: pull idl changes (#1472)

feat: Expose cluster attribute type (#1470)

feat!: Introduce ListFailoverHistory and active-active refactoring fr…

…om IDL (#1468)

<!-- Describe what has changed in this PR -->
**What changed?**
**Detailed Description**
- Pull latest changes from active-active

<!-- Tell your future self why have you made these changes -->
**Why?**
We redesigned and reimplemented active-active domains feature and made some breaking changes to IDL.

<!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? -->
**How did you test it?**
unit tests

<!-- Assuming the worst case, what can be broken when deploying this change to production? -->
**Potential risks**
This might be a breaking change, but we only broke changes available in release candidates and they're not available in any formal release.

**Impact Analysis**
- **Backward Compatibility**: N/A Since introducing a new endpoint
- **Forward Compatibility**: N/A

**Testing Plan**
- **Unit Tests**: We have unit tests for these changes
- **Persistence Tests**: N/A
- **Integration Tests**: tested with integration tests
- **Compatibility Tests**: N/A

**Rollout Plan**
- What is the rollout plan? Rollout wave by wave starting from staging
- Does the order of deployment matter? No
- Is it safe to rollback? Does the order of rollback matter? Yes
- Is there a kill switch to mitigate the impact immediately? No

Introduce FailoverDomain endpoint

feat: Adds helpers, documentation for experimental blocks feature (#1460

)

* Adds experimental blocks feature

Add support for Ephemeral TaskLists (#1449)

Update Sessions to use Ephemeral TaskLists behind a feature flag. This ensures that the per-host TaskList is automatically removed once it is no longer used.

This should only be enabled once the server fully supports Ephemeral TaskLists as it will otherwise return errors for the unknown TaskListKind.

Signed-off-by: Nathanael Mortensen <natemort@uber.com>

Support passing the specified QueryConsistencyLevel (#1456)

<!-- Describe what has changed in this PR -->
**What changed?**

Updated mappers for `DescribeWorkflowExecutionRequest` and `GetWorkflowExecutionHistoryRequest`. 

<!-- Tell your future self why have you made these changes -->
**Why?**

When implementing the ability to pass QueryConsistencyLevel: Strong on DescribeWorkflowExecution and GetWorkflowExecutionHistory I missed two mappers to convert between proto and thrift objects. This meant that requests passed via the go client did not have the user defined consistency level and passed the default, Invalid.  
 
<!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? -->
**How did you test it?**

Unit tests + tested w/ a local script using the go client against our staging environments. 


<!-- Assuming the worst case, what can be broken when deploying this change to production? -->
**Potential risks**

N/A

Autoscaler empty poll fix (#1455)

What changed?

activityWorker poll should populate autoConfigHint
workflowWorker poll additional field population. This is optional but is good to have it
Why?

Activity worker doesn't process auto config hint on empty polls

How did you test it?

Unit Test

Local Test with Cadence-Samples. Now it's scaling down correctly on empty poll scenarios

Fix mapping for cancel cause for proto requests (#1454)

Pretty simple / clear missing field. No real reason to suspect other fields are similar, so I think this is all that's necessary, but it'd be really nice to have a "must fill all struct fields" linter :|