chore: Delete obsolete FlowFixMe comments

[pedrottimark]

Summary

As far as I can find, this is the last of them:

• 1 in ./e2e/__tests__/detectOpenHandles.ts
• 2 in ./e2e/__tests__/iterator-to-null-test.ts
• 3 in ./e2e/__tests__/snapshot.test.ts
• 1 in ./e2e/__tests__/snapshotMockFs.test.ts
• 1 in ./e2e/__tests__/snapshotResolver.test.ts
• 1 in ./e2e/__tests__/snapshotSerializers.test.ts

EDIT here is the command that I used to find those file in the project:

fgrep -lr --exclude-dir 'node_modules' --include '*.[j|t]s' '$FlowFixMe' .

Test plan

Local lint and tests, and then CI

[thymikee]

Hope that's everything? Do we have any dangling "@flow" references maybe? Also it's an internal cleanup change so I do think it needs a changelog, but whatever :)

[codecov-io]

Codecov Report

Merging #8885 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #8885   +/-   ##
=======================================
  Coverage   64.11%   64.11%           
=======================================
  Files         275      275           
  Lines       11623    11623           
  Branches     2846     2845    -1     
=======================================
  Hits         7452     7452           
  Misses       3545     3545           
  Partials      626      626

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 700c17c...9f234d0. Read the comment docs.

[SimenB]

Grep for @flow comments as well?

[pedrottimark]

Good thinking, my friends. I will delete 16 occurrences of @flow under e2e

Here are 3 files that I am not sure whether to delete or keep the comment:

./examples/react-native/index.android.js
./examples/react-native/index.ios.js
./examples/react-native/Intro.js

so I do think it needs a changelog

If you mean do not then I am happy to get rid of it. Less is more :)

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.