Trigger notification if MyDrive scan times out when scanning a user

Description

Failure to scan a user's MyDrive to remove their sharing permissions has a timeout that then sets the user in to a "needs manual attention" state for attention. No notification that this has happened is made.

Further details

The listing of files in a user's space has a timeout (max_user_scan_duration). The scan_remove_users_shared_permissions function catches this and prepends the user's custom action state with "manual-". These users will then (indefinitely) be ignored by future process. Only running the 'reset-manual' operation (or manually changing in the admin console) do these users get reprocessed.

Task list

• Trigger a notification if a scheduled run set at least one user in to this "needs manual attention" state.

Potential solution

Failing (return non-zero) will cause the pipeline to fail and automatically trigger a notification.

Acceptance criteria

• Future automated runs of the MyDrive scan operation notify the DevOps Wilson team when users get set in to a "needs manual attention" state.