Incorporate/document procedure for toggling notifications around LPDAAC maintenance windows

[chuckwondo]

When LPDAAC performs maintenance in their Prod and UAT environments, we must:

• disable notifications prior to maintenance
• enable notifications after maintenance

LPDAAC informs us of maintenance via the lp-coordination channel in the Slack HLS-Processing workspace. For example: https://hls-processing.slack.com/archives/C024LQY0MC5/p1709760574421079

Disabling and enabling is currently performed manually. Missed notifications are resolved via the reconciliation process.

Manual changes to notifications are performed by manually changing the suffix value for the event notification attached to the appropriate bucket: hls-dev-global-v2-forward for UAT, and hls-global-v2-forward for Prod. The correct suffix is v2.0.json, and this is typically changed to v2.0.json.stopped to disable notifications, and subsequently changed back to v2.0.json to re-enable notifications.

At a minimum, we must document this procedure, but ideally, we design a better approach and document that approach.