Revise cross-functional review timing and scope

Why is this change being made?

Revise the timing to take into account:

• When product manager are done planning for the next release, which generally 1 day after the previous release ends so they an know what issues made the previous release
• When any automation has run that moves issues that missed the last release and move them to the current release
• Two days after the above, as the SLO on replicating changes from the production postgres database to snowflake/sisense is 48 hours

This MR also clarifies sub-department level reviews and the company-wide review.

We want to do these reviews as soon as the data is accurate because we need to analyze accurate trends and we want to do the review early enough to influence the current release for any critical feedback.

Related: Update cross-functional review process based on... (!108371 - merged)

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.

---