Update schedule for AMER timezone

Why is this change being made?

To make it easier for the AMER Release manager to deploy as frequently as possible. Currently they are only able to see 1 deploy, and must wait over an hour before being able to deploy the next package. This is not in alignment with the team member schedule.

Adjusting the time frame should enable us to create a package sooner enabling them to deploy more frequently.

Addresses: gitlab-org/release/tasks#4176 (closed)

Milestones

• This is approved
• This is merged
• The schedule of the auto-deploy branch is updated: https://ops.gitlab.net/gitlab-org/release/tools/-/pipeline_schedules/73/edit

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---