[active-active] Add active cluster selection policy to workflow start

[taylanisikdemir]

Summary

[Brief summary of the change, including the rationale and intended effect]
Active cluster selection policy will be applicable to active-active domains. More details on active-active mode can be found here.

Type of Change

• Add new API(s)
• Add new data type(s)
• Add new field(s) to existing data type
• Remove field(s) from data type
• Remove data type(s)
• Remove API(s)
• Other (please provide detailed description)

Data Effect

• Does it change the data stored in database?

Detailed Description

[In-depth description of the changes made to the IDL, specifying new fields, removed fields, or modified data structures]
There will be a new field in workflow execution info. This is mostly for informational purposes.
There is going to be a new row type to store the policy for wf-runid pair which will be used by frontend to determine active region/cluster to forward accordingly.

Impact Analysis

• Backward Compatibility: [Analysis of backward compatibility]
  Changes are backward compatible. No impact until server starts using these.
• Forward Compatibility: [Analysis of forward compatibility]

Testing Plan

• Unit Tests: [Do we have unit test covering the change?]
• Persistence Tests: [If the change is related to a data type which is persisted, do we have persistence tests covering the change?]
• Integration Tests: [Do we have integration test covering the change?]
• Compatibility Tests: [Have we done tests to test the backward and forward compatibility?]

Rollout Plan

• What is the rollout plan?
• Does the order of deployment matter?
• Is it safe to rollback? Does the order of rollback matter?
• Is there a kill switch to mitigate the impact immediately?

[timl3136]

I think we should fix the enum naming before merging

The requested change is minor and won't break system