feat: Add cron and execution related fiedls to visibility

[neil-xie]

Summary

[Brief summary of the change, including the rationale and intended effect]
Add CronSchedule, ExecutionStatus and ScheduledExecutionTime to visibility workflow execution info

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]
Adding CronSchedule, ExecutionStatus and ScheduledExecutionTime fields to workflowExecutionInfo and new enum for workflowExecutionStatus

Impact Analysis

• Backward Compatibility: [Analysis of backward compatibility] Yes
• Forward Compatibility: [Analysis of forward compatibility] Yes

Testing Plan

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

Rollout Plan

• What is the rollout plan? pull into cadence repo
• 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]

LGTM

[timl3136]

since we are adding cronSchedule field, perhaps we can think about removing this field in the future