chore(deps): update dependency @react-native-async-storage/async-storage to v2 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@react-native-async-storage/async-storage (source)	1.x → 1.x || 2.x

---

Release Notes

react-native-async-storage/async-storage (@​react-native-async-storage/async-storage)

v2.2.0

Compare Source

Minor Changes

• 8b2f32b: Fix support for React Native 0.80

v2.1.2

Compare Source

Patch Changes

• 21d0c22: Remove unnecessary getViewManagers overrides

v2.1.1

Compare Source

Patch Changes

• 5042047: Mark some methods as nonnull

v2.1.0

Compare Source

Minor Changes

• b7c842c: Windows: Add New Architecture support

v2.0.0

Compare Source

Major Changes

• c319205: Support 0.74 (by migrating off deprecated onCatalystInstanceDestroy) — unfortunately, this also means that we must bump the minimum supported version to 0.65

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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 was generated by Mend Renovate. View the repository job log.

[bkrem]

@ignaciosantise is it safe for us to upgrade this?

See changelog above:

[v2.0.0](https://redirect.github.com/react-native-async-storage/async-storage/releases/tag/%40react-native-async-storage/async-storage%402.0.0)
[Compare Source](https://redirect.github.com/react-native-async-storage/async-storage/compare/@react-native-async-storage/async-storage@1.24.0...@react-native-async-storage/async-storage@2.0.0)

Major Changes
[c319205](https://redirect.github.com/react-native-async-storage/async-storage/commit/c319205): Support 0.74 (by migrating off deprecated onCatalystInstanceDestroy) — unfortunately, this also means that we must bump the minimum supported version to 0.65

[ignaciosantise]

@bkrem according to the changelog, it should be safe. I didn't test 2.0 version yet