Suggest FCL format for weekly standups, update when VP approvals are needed for FCLs

Why is this change being made?

• It seems the agenda format was missing. Added it to this MR.
• We should expect that all S1 and customer-facing S2s incidents will have an FCL associated. The exception cases is where VP approval is needed. Currently the handbook states that all FCLs are subject to VP approval, but I believe we should expect them by default (e.g. auto-approved) if they meet the S1/S2 incident criteria as described.

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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• 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.

---