Timer Trigger: Log more details on ScheduleStatus to improve debugging

[cjaliaga]

When the ScheduleMonitor stores the status it currently saves:

{
    "Last": "2024-04-03T20:48:28.1075034+00:00",
    "Next": "2024-04-04T01:00:00+00:00",
    "LastUpdated": "2024-04-03T20:48:28.1075034+00:00"
}

However, we've seen situations such missing logs in Kusto where we know an execution happened (the status file was updated) but we don't know details such the invocation id or the instance that ran that invocation. Adding these details to the ScheduleStatus would help debugging those issues.

Internal ICM: 494605503