(DOCSP-33539): React Native: Update Create & Manage User API Keys to use auth hooks

[dacharyc]

Pull Request Info

Jira ticket: https://jira.mongodb.org/browse/DOCSP-33539

• Authenticate Users
• Create & Manage User API Keys

This PR adds to the React Native test suite, enabling us to test API user auth in a more robust way. The React Native tests in general are still somewhat flaky in CI - some of them are failing the CI for this PR but pass locally. These are mostly related to tests that make network requests. The pattern established in this PR should help address network issues and make tests more reliable in CI.

Essentially, the test is more an integration test than a unit test. I recommend we go to this higher-level testing for most networking aspects for examples that integrate with UI elements.

Reminder Checklist

Before merging your PR, make sure to check a few things.

• Did you tag pages appropriately?
  • genre
  • meta.keywords
  • meta.description
• Describe your PR's changes in the Release Notes section
• Create a Jira ticket for related docs-app-services work, if any

Release Notes

• React Native SDK
  • Manage Users/Authenticate Users: Update information and code example for logging in with an API key.
  • Manage Users/Create & Manage User API Keys: Update information and code examples for creating, deleting, enabling, and disabling API keys from the client.

Review Guidelines

REVIEWING.md

[krollins-mdb]

Currently getting the following error or one about no refresh token on the last bit of the test.

http error code considered fatal. Client Error: 403

This only happens in the Jest test. Everything works in the simulator. Trying to figure it out.

[netlify]

✅ Deploy Preview for device-sdk ready!

Name	Link
🔨 Latest commit	fdda3b4
🔍 Latest deploy log	https://app.netlify.com/sites/device-sdk/deploys/66913c3fecdfe30007bb5be9
😎 Deploy Preview	https://deploy-preview-3180--device-sdk.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[github-actions]

Readability for Commit Hash: fdda3b4

You can see any previous Readability scores (if they exist) by looking
at the comment's history.

Readability scores for changed documents:

• source/sdk/react-native/manage-users/manage-user-api-keys: Grade Level: 5.8, Reading Ease: 75.61
• source/sdk/react-native/manage-users/authenticate-users: Grade Level: 9.1, Reading Ease: 50.94

For Grade Level, aim for 8 or below.

For Reading Ease scores, aim for 60 or above:

Score	Difficulty
90-100	Very Easy
80-89	Easy
70-79	Fairly Easy
60-69	Medium
50-59	Fairly Hard
30-49	Hard
0-29	Very Hard

For help improving readability, try Hemingway App.

[dacharyc]

I think the new approach re: the steps is clever! But I don't love that this creates a dependency chain from step N to step N. We have been trying to move to making our tests more separated, and eliminate inter-dependencies - so it seems like this is moving in the opposite direction. Maybe we could talk offline about this shift in approach?

[dacharyc]

I think I would like to see a heading between this intro bit and the @realm/react info. It would be nice to have this as a scannable heading in the OTP. i.e. something like:

API Key Auth with @realm/react

Or:

React Hooks

Or something that indicates this is the info about how to use this with hooks.

[krollins-mdb]

That makes sense. Thank you for pointing this out!

[krollins-mdb]

Dachary has reviewed and approved, but since this was originally her PR, she can't approve it on GitHub. So, I'm approving in her place. 😄

[docs-builder-bot]

✨ Staging URL: https://preview-mongodbmongodb.gatsbyjs.io/realm/master/

🪵 Logs

• job log: cbe9d6139bd7f29ba93b0897596d3e157e3a5da5