Comment out failing circle ci test

[Saad Najmi (Saadnajmi)]

Please select one of the following

• I am removing an existing difference between facebook/react-native and microsoft/react-native-macos 👍
• I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos 👍
• I am making a fix / change for the macOS implementation of react-native
• I am making a change required for Microsoft usage of react-native

Summary

The Flow Check phase of our End to End Circle CI tests fails. This seems to be because the E2E test is installing _react-native-macosversion 0.63 instead of latest (which is missing theColors.darker` variable, which is how I figured that out. I haven't figured it out yet (perhaps #944 will help?), but this is blocking PRs quite a bit. Let's comment it out for now

Changelog

[Internal] [Removed] - Removed Flow check test from E2E tests temporarily

Test Plan

[Pull Request Analyser (pull-bot)]

	Fails
🚫	❗ Base Branch - The base branch for this PR is something other than master. Are you sure you want to target something other than the master branch?

Generated by 🚫 dangerJS against 21cdb45

[Saad Najmi (Saadnajmi)]

HeyImChrisHarrie Shin (@harrieshin) The failing circle-ci tests now pass, and #946 should take care of the analyze_pr check

[HeyImChris]

Looks like the CI is still failing? If we can keep most CI tests in tact and passing then that's great. We also don't really rely on CircleCI much anyway so could do away with them too

[Saad Najmi (Saadnajmi)]

Looks like the CI is still failing? If we can keep most CI tests in tact and passing then that's great. We also don't really rely on CircleCI much anyway so could do away with them too

test_js and test_js_prev_lts both now pass. The failing "analyze_pr" is bc of danger bot which I fixed with #946