Clarify communicating a feature flag rollout

What does this MR do?

This MR clarifies how and when to communicate a feature flag rollout with other parts of the company.

The motivation for this MR was a checkbox in a Feature Flag Rollout issue #207351 (closed):

Coordinate a time to enable the flag with #production and #g_delivery on slack.

There was no guidance in our feature flag rollout process around when this was necessary.

Author's checklist

• Follow the Documentation Guidelines and Style Guide.
• [-] If applicable, update the permissions table.
• [-] Link docs to and from the higher-level index page, plus other related docs where helpful.
• Apply the documentation label.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.