Support creating workflows with ClusterAttributes for active-active domains

[c-warren]

Is your feature request related to a problem? Please describe.

cadence-workflow/cadence#6697 has added support for active-active domains. These domains allow specifying a ClusterAttribute (a scope:name pair) on which workflows can be sub-divided. Each set of workflows with a given clusterAttribute independently determine their active cluster - allowing multiple clusterAttributes to be active on different clusters simultaneously.

To do this, workflows can be started with an optional ClusterAttribute. The Java client should be modified to support this.

Proposed Solution

To support active-active we must:

Ensure that the ClusterAttribute IDLs have been pulled into the client
Update generated code to support the new request types
Update mappers to support the new fields
Any other tweaks required

Note: This may also require implementation of FailoverHistory, a new API that supports retrieving the failover history of all domains - particularly w.r.t active-active domains.

These are some of the relevant PRs in the go-client:
cadence-workflow/cadence-go-client@cf0b546#diff-ad8d5a0456b333216cb6f9e99fd8c4b79d2f8ef8e28abd2fc3fa2b3da7ed1bd4
https://github.com/cadence-workflow/cadence-go-client/pull/1469/changes
https://github.com/cadence-workflow/cadence-go-client/pull/1470/changes

Additional context
Add any other context or screenshots about the feature request here.

N/A