Create a new scheduled task to check security review launch bug statuses

[DanielRyanSmith]

This is part of the work for integrating ChromeStatus with IssueTracker API in order to create and reference security review bugs. A new scheduled task should be created to periodically check the status of security review launch bugs that are associated with features and update the security gates associated with those features based on the approval status.

To maintain review approval status in ChromeStatus, existing launch bugs can be monitored using a scheduled task system, in which a periodic request is sent from ChromeStatus to a new OT API endpoint, TrialsIntegration.BatchGetLaunchBugStatus (this request is planned for running on a 2-hour interval (*), but can be adjusted as needed during implementation). For launch bugs that are marked as “Approved” and are associated with features that have not been updated in the past 14 days, the periodic bug update can occur on a less frequent interval (this request is planned for running on a 7-day interval (*), but can be adjusted as needed during implementation). The request contains a list of launch bug IDs that require an update check. The endpoint will obtain relevant bug information (specifically status) using IssueTracker.BatchGetIssues. The status for each given launch bug ID will be returned in the response to ChromeStatus. This status will be used to update the “WP Security” gate states for each stage.

(*) Request intervals can be updated as needed if it positively affects usability and efficiency.

The scheduled task can be defined in maintenance_scripts.py. Follow the structure in this PR as an example.

Approval state mapping

Launch bug status	ChromeStatus gate status
New	No Response
Assigned	Review Started
In Progress (Accepted)	Review Started
Fixed (all variations)	Approved
Won’t Fix (all variations)	Denied
Duplicate	(Take action to find a valid launch bug)