chore(deps): update dependency react-native-camera to v4.2.1

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
react-native-camera	4.0.3 -> 4.2.1

---

Release Notes

react-native-community/react-native-camera

v4.2.1

Compare Source

Bug Fixes

• Remove the mCamera.setPreviewDisplay call on surface destroy as it may cause ANRs or slow down the UI when unmounting. The side effect of this is a nasty warning BufferQueue has been abandoned that can be ignored. (#​3331) (9c0b87e)

v4.2.0

Compare Source

Features

• added hasTorch method (#​3340) (f7fbbbf)

v4.1.1

Compare Source

Bug Fixes

• default variable to empty string to match RN props (#​3330) (4523c06)

v4.1.0

Compare Source

Features

• implement onCameraReady event on Windows (#​3324) (7b897b0)

v4.0.3

Compare Source

Bug Fixes

• Missing TS type definition (#​3320) (01333a9)

v4.0.2

Compare Source

Bug Fixes

• Improve surface destroy handling. (#​3316) (5d36cf1)

v4.0.1

Compare Source

Bug Fixes

• Workaround for hardware JPEG rotation bug on some Samsung devices (#​3305) (381f958), closes /github.com/react-native-camera/react-native-camera/issues/3060#issuecomment-892583205 /github.com/react-native-camera/react-native-camera/pull/3305#issuecomment-893819348

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate[bot]]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you check the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @nartc/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   dev react@"16.13.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"17.0.1" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   dev react-native@"0.64.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2021-09-21T20_21_48_404Z-debug.log