feat!: Introduce ListFailoverHistory and active-active refactoring from 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

Author: Shaddoll