implemented isGreen functionality to verify whether a commit SHA is promote-able (#79061)
Relates to #76700
**Overview:** I implemented the isGreen method in `print_latest_commits.py` which takes in a commit SHA and returns if the commit is promote-able to viable/strict. I use a regex for checks that must be successful, and a short allow-list for the checks that can either be success or skipped. If a commit SHA is not promote-able, the method will output a short error message specifying which workflow name (ex: pull, android-tests) that had unpromote-able check results.
**Example Outputs:**
Example of a promote-able SHA:
![Screen Shot 2022-06-07 at 5 08 44 PM](https://user-images.githubusercontent.com/24441980/172483287-84eb414d-e431-4fca-bb20-61ac3d9c9b69.png)
![Screen Shot 2022-06-07 at 5 08 52 PM](https://user-images.githubusercontent.com/24441980/172483298-27874f5e-30fd-4bc1-b50b-a2293311a265.png)
This matches the current viable/strict branch as this SHA is part of viable/strict on the HUD.
Example of an unpromote-able SHA:
![Screen Shot 2022-06-09 at 11 40 55 AM](https://user-images.githubusercontent.com/24441980/172888402-b627556b-03a9-411c-9024-f017730cfaa6.png)
![Screen Shot 2022-06-09 at 11 41 14 AM](https://user-images.githubusercontent.com/24441980/172888455-e9ab10bc-ed62-476d-9835-045338494f9c.png)
**Test Plan:** Compare commit SHAs with those found on the viable/strict branch on the HUD. I have also looked manually at the check results for commits on the HUD in the master branch to see if they are green and promoteable to viable/strict. Since I did not use the original specifications for green-ness that were mentioned in #76700, I will modify my test cases in the next PR.
Pull Request resolved: https://github.com/pytorch/pytorch/pull/79061
Approved by: https://github.com/seemethere