Bump tough-cookie and realm in /apps/NortheastOhioBingo

[dependabot]

Removes tough-cookie. It's no longer used after updating ancestor dependency realm. These dependencies need to be updated together.

Removes tough-cookie

Updates realm from 11.10.1 to 12.2.1

Changelog

Sourced from realm's changelog.

12.2.1 (2023-10-05)

Deprecations

• Realm.User.providerType is deprecated, and will be remove in next major version. Use Realm.User.identities instead.

Fixed

• Outside migration functions, it is not possible to change the value of a primary key. (#6161, since v12.0.0)
• Receiving a write_not_allowed error from the server would have led to a crash. (realm/realm-core#6978, since v11.5.0)
• If querying over a geospatial dataset that had some objects with a type property set to something other than Point (case insensitive) an exception would have been thrown. Instead of disrupting the query, those objects are now just ignored. (realm/realm-core#6989, since v12.0.0)
• If a user was logged out while an access token refresh was in progress, the refresh completing would mark the user as logged in again and the user would be in an inconsistent state. (realm/realm-core#6837, since v10.0.0)
• Logging in a single user using multiple auth providers created a separate Realm.User per auth provider. This mostly worked, but had some quirks:
  • Sync sessions would not necessarily be associated with the specific Realm.User used to create them. As a result, querying a user for its sessions could give incorrect results, and logging one user out could close the wrong sessions.
  • Existing local synchronized Realm files created using version of Realm from August - November 2020 would sometimes not be opened correctly and would instead be redownloaded.
  • Removing one of the Realm.Users would delete all local Realm files for all Realm.Users for that user.
  • Deleting the server-side user via one of the Realm.Users left the other Realm.Users in an invalid state.
  • A Realm.User which was originally created via anonymous login and then linked to an identity would still be treated as an anonymous users and removed entirely on logout.
  • realm/realm-core#6837, since v10.0.0

Compatibility

• React Native >= v0.71.4
• Realm Studio v14.0.0.
• File format: generates Realms with format v23 (reads and upgrades file format v5 or later for non-synced Realm, upgrades file format v10 or later for synced Realms).

Internal

• Upgraded Realm Core from v13.20.1 to v13.22.0. (#6158)

12.2.0 (2023-09-24)

Deprecations

• Realm.App.Sync.reconnect(app) has been deprecated and will be removed in the next major version. You can use Realm.App.Sync.Session.reconnect() instead.

Enhancements

• Added Realm.Sync.Session.reconnect() to help force a reconnection to Atlas Device Sync. (#6123)
• Added Realm.App.AppConfiguration.metaData which will make it possible to encrypt metadata used by the Realm.App. (#6147)

Fixed

• Fixed values of properties being replaced by default value when updating. (#6129, since v12.0.0)
• Fixed that value for Realm.schemaVersion wasn't propagated correctly for non-existing files. (#6119, since v12.0.0)
• Full text search supports searching for prefix only e.g., description TEXT 'alex*'. (realm/realm-core#6860)
• Unknown protocol errors received from the Altas Device Sync server will no longer cause the app to crash if a valid error action is also received. Unknown error actions will cause device sync to fail with an error via the sync error handler. (realm/realm-core#6885)
• Allow arguments to Realm Query Language to be a string representation of a geospatial object for GEOWITHIN queries. (realm/realm-core#6934)
• Crash when querying the size of a Object property through a link chain. (realm/realm-core#6915, since v12.0.0)
• Throw an exception when some limitation on the OS filesystem is reached, instead of crashing the application. The same file locking logic is now also used for all the platforms. (realm/realm-core#6926)
• Fixed crash that generated the error message Assertion failed: ref + size <= next->first. (realm/realm-core#6340, since v11.3.0)
• When using OpenSSL (i.e. on non-Apple platforms) a TLS handshake error would never be reported and instead TLS errors would be reported as a sync connection failure. When using SecureTransport (i.e. on Apple platforms) only some TLS handshake errors would be reported, but most were reported as a sync connection failure. Additionally, reported sync errors originating from OpenSSL have been improved. (realm/realm-core#6938).
• Fixed Bad server version errors and client reset which sometimes occurred when updating a subscription's query. (realm/realm-core#6966, since v10.12.0)

Compatibility

• React Native >= v0.71.4
• Realm Studio v14.0.0.

... (truncated)

Commits

• 5e42625 [12.2.1] Bump version (#6177)
• 0eb9ee3 Revert version change
• 06e073c New README.md strategy (#6176)
• ab2ee63 Symlinking (#6173)
• ea679c4 Upgrade to Realm Core v13.22.0 (#6167)
• f54ba83 Include age in schema (#6171)
• 9913451 Disallow changes to value of primary key columns outside migration (#6162)
• 35707e6 [12.2.0] Bump version (#6154)
• 3e1a4b5 Expose metadata persistence modes on App configuration (#6152)
• 471c31b Upgrade to Core v13.20.1 (#6151)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.