Update for weekly Epic status 'due by' timing

Both Engineering Cross-Functional DRIs should provide weekly updates for the DRI's epics according to following process, which allows alignment with [Project Management in Platforms](/handbook/engineering/infrastructure-platforms/project-management/#project-management-in-platforms):

1. **By Wednesday at 21:00 UTC** the DRI for a project is expected to update the status block in the epic description to:

    1. Format for weekly update: **Date of Update** (YYYY-MM-DD)

1. **By Thursday EoD (Friday 02:00 UTC)** the DRI for a project is expected to update the status block in the epic description to:

    1. Format for weekly update: Should follow the [Epic status automation format](https://gitlab.com/gitlab-com/gl-infra/epic-issue-summaries/-/blob/master/lib/status_note/epic_updater.rb)

    1. Brief update for each of these four areas:

        1. Indicate project [Health Status by label](/handbook/engineering/infrastructure-platforms/gitlab-dedicated/#workflow-labels).

        1. Briefly highlight project status.

The update schedule is designed to cascade information up through these levels:

- **Thursday EoD**: DRIs update project epics (automation prompts at Thursday 00:00 UTC)

- **Thursday EoD (Friday 02:00 UTC)**: DRIs update project epics (automation prompts at Thursday 00:00 UTC)

- **Friday**: Leads update Grand Review and GOM Functional Lead epics using the information from Thursday

- **Monday**: Leadership team discusses updates

- **Tuesday**: Platforms Grand Reviews occur