Fix: Updated yarn.lock hash for react-native-mock

[jglover]

Updates hash for react-native-mock to match expected 96bee7b072cea66f5dfa21c39b2416ca6fb6c0da.
This also causes some cascading changes in the lock file after running yarn (install) again so should be treated with caution.
Tested on Android (physical) and iOS simulator.

[alejandronanez]

What command did you run to update the yarn.lock file? Modifying directly yarn.lock is not good.

Also, welcome thanks for your first contribution!

[jouderianjr]

hey @alejandronanez I think he just deleted the yarn.lock and ran yarn install again, I did that and worked in my env 😄

[jglover]

Just to give some background, I updated the hash via yarn remove and yarn add, I believe the hash may have been wrong originally because someone updated the file manually, probably resolving a conflict gone bad?
The other changes were caused by running yarn afterwards, which I believe has caused it to add dependencies for react-native-mock whilst also making sure it has all the versions required by peer dependencies.

[andrewda]

Guessing the issue was b/c I used the fork instead of the original and didn't do it through yarn. Thanks for the fix!