Update yarn.lock

[mkcode]

This yarn.lock file was regenerated by deleting the existing yarn.lock file and rerunning yarn install.

Summary

The current yarn.lock file is fairly out of date and is affecting the CI servers.

More specifically, fsevents@1.2.7, referenced in yarn.lock here, fails to compile on node 12 or later.

This causes the yarn install step on CI to error.

This PR is being made as 1 step in getting the RNTester detox tests running again.

We can alternatively manually update the yarn.lock file with the minimum needed fsevent changes if this PR changes too much.

Changelog

[Internal] [Changed] - Bump fsevents from 1.2.7 to 1.2.13.

Test Plan

Verify yarn install step on CI is fixed.

[mkcode]

Yarn install step on CI looks better with these changes: https://app.circleci.com/pipelines/github/facebook/react-native/7069/workflows/ce93e1d1-64a5-4bfe-9798-d9744dcd8505/jobs/176303/parallel-runs/0/steps/0-104

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
ios	-	universal	n/a	--

Base commit: 0e9296b

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	7,524,788	+0
android	hermes	armeabi-v7a	7,110,030	+0
android	hermes	x86	7,965,256	+0
android	hermes	x86_64	7,876,556	+0
android	jsc	arm64-v8a	8,989,250	+0
android	jsc	armeabi-v7a	8,557,601	+0
android	jsc	x86	8,991,225	+0
android	jsc	x86_64	9,542,782	+0

Base commit: 0e9296b

[cpojer]

Can you instead only remove fsevents from yarn.lock and re-run Yarn? We don't want all dependencies to be updated like this.

[mkcode]

@cpojer - Changes made and yarn install step on CI looks good. The 1 CI failure is the same as master.

[cpojer]

Nice, that's much better!

[facebook-github-bot]

@cpojer has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[react-native-bot]

This pull request was successfully merged by @mkcode in 0bbab02.

^{When will my fix make it into a release? | Upcoming Releases}