[android] [dev] Update modules that were patched for AndroidX compatibility

[southerneer]

for #3832 we patched a bunch of packages. Eventually all of these packages will update their Android dependencies to AndroidX style. We should update our dependencies accordingly (and remove associated patches).

• bugsnag-react-native
• react-native
  • [dev] Upgrade to RN 0.60.0 #3886
• rn-action-sheet
• rn-android-open-settings
• rn-background-geolocation
• rn-camera-kit
• rn-code-push
• rn-config
• rn-contacts
• rn-device-info
• rn-extra-dimensions
• rn-firebase
  • https://rnfirebase.io/docs/v5.x.x/releases/v5.5.x
  • v5.5.5 works great on iOS, but still requires jetify to work on Android.
  • v6.0.0 has been WIP for a few months now and will presumably include AndroidX updates so we should probably just wait for that
• rn-fs
  • waiting on this PR to get merged and published: Add androidx suppport. itinance/react-native-fs#691
• rn-gesture-handler
  • waiting for one of the open AndroidX PRs to get merged and published
• rn-image-crop-picker
  • waiting for a PR merge: https://github.com/ivpusic/react-native-image-crop-picker/search?q=androidx+is%3Apr&type=Issues
• rn-linear-gradient
• rn-localize
• rn-maps
  • we're on the latest version. There have been some commits (not yet published to npm) to allow jetifier to run well against rn-maps, but no updates specifically for AndroidX compatibility
  • I don't understand why this PR was closed...it was submitted by the guy who made jetifier and had positive feedback from the repo maintainers.
• rn-mixpanel
• rn-pure-jwt
• rn-push-notifications
• rn-splash-screen
  • waiting on PR merge: Androidx upgrade crazycodeboy/react-native-splash-screen#355
• rn-touch-through-view

[southerneer]

@bengtan @aksonov this will probably be a gradual process rather than solved in one PR. We shouldn't pursue this until after the upcoming iOS release.

[bengtan]

@southerneer:

What's your plan for this?

Are you going to do one iteration of trying to upgrade/patch as many modules listed (in the OP) as possible?

---

Ticket #3789 might overlap with this.

[southerneer]

I was thinking of doing a pass over each module in the list and pick off the ones that are easy upgrades (like bugsnag). Presumably there will be some that still lack AndroidX compatibility and may not make sense to upgrade...I'll create separate tickets for those to either check in the future or do the upgrade work in a fork and submit as an upstream PR.

[southerneer]

@mstidham this one isn't directly QA-able, we're basically just trying to avoid regressions or lost functionality. I smoke-tested all of the updates, but will await your results too. Push notifications I would pay the most attention to.

[bengtan]

Moving this back to Ready because there's some more follow-up dev work.

[bengtan]

@southerneer: What do you think of closing this ticket?

Most of this work is done, and with dependabot, we'll eventually update all the remaining ones ... eventually.

Yes, there is still work to be done, but we don't really need a dedicated ticket (ie. this one) to track it, I think.