[CU] Update to Expo 50 and Storybook 7

[narin]

Description of Change

This ticket started out as attempting to fix the Android font loading in #98. I suspected that updating to the latest Expo SDK 50 would resolve this. Doing this resulted in errors in Storybook so I decided to update Storybook to v7 as well.

• Update Expo, Storybook, and related packages packages to latest
• Followed @storybook/react-native migration guide, modifying metro.config.js and stories to use updated syntax
• Deleted local fonts and import them from our assets package using the inline require()
• This ended up fixing the Backgrounds addon that was previously disabled because it conflicted with the dark/light mode toggle
• Updated Storybook to use autodocs
  • Note: We were previously using the generateDocs parameter to generate a custom docs template with the documentation link. This seemed to work still, however code snippets were broken. This appears to be a bug with Storybook. I've instead added the documentation link in the comments above each component so we can retain this link. I've created a bug ticket #176 to follow up and fix this in the future.
• Updating to the latest storybook version should also fix the dependabot security alerts, although we won't know for sure until this code is merged to main
• Also fixes #171

Testing Packages

• 0.5.2-alpha.3 to 0.5.2-alpha.9

Screenshots/Video

Web

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/d2415bd3-4966-4f65-a4aa-f8467d63e685

iOS

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/fcbbe144-aa2a-4954-909a-e7310d2b64ef

Android

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/a7479080-fd93-4452-ad13-6513aa9e1ae4

VA Mobile iOS

VA Mobile Android

Testing

• [x] Tested on iOS
• [x] Tested on Android
• [x] Tested on Web

PR Checklist

Code reviewer validation:

• General
  • [x] PR is linked to ticket(s)
  • [x] PR has changelog label applied if it's to be included in the changelog
  • [x] Acceptance criteria:
    • All satisfied or
    • Documented reason for not being performed or
    • Split to separate ticket and ticket is linked by relevant AC(s)
  • [x] Above PR sections adequately filled out
  • [x] If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket
• Code
  • [x] Tests are included if appropriate (or split to separate ticket)
  • [x] New functions have proper TSDoc annotations

Publish

If changes warrant a new version per the versioning guidelines and the PR is approved and ready to merge:

• [x] Merge main into branch
• [x] Merge branch to main
• [x] Publish new version after merging

[TimRoe]

Guess we can't quite find out yet, but wonder if the Storybook update might also fix #171 to swing for 6 tickets with one PR.

[TimRoe]

May be good to cut an alpha build and spot check flagship. Nothing in particular sticks out as concerning and the changes are mostly in files that have no bearing, but seems like it'd be good to validate the removal of the App. bit is definitely good--it should be, but was previously a hard red error on load in flagship so probably good to confirm.

[TimRoe]

Don't need to go out of your way, but with the initial round of Link now in this branch, may be worth checking if it fixed #171 to update Storybook/Expo to add another ticket smote by this PR.

[narin]

May be good to cut an alpha build and spot check flagship. Nothing in particular sticks out as concerning and the changes are mostly in files that have no bearing, but seems like it'd be good to validate the removal of the App. bit is definitely good--it should be, but was previously a hard red error on load in flagship so probably good to confirm.

Tested within the App. Moving webStorybookColorScheme() back into utils/index.tsx brought back errors about window being undefined. I moved webStorybookColorScheme() into storybook.tsx and loaded it conditionally within a try/catch which resolved the errors in the App. I also did some cleanup to consolidate the color scheme hook in utils/index.jsx so that we don't have to keep doing webStorybookColorScheme() || useColorScheme() and can instead just import useColorScheme from utils and have the logic handled inside there.

App testing screenshots added in PR description above.

Finally, I also fixed #171. This was due to a typo in the font import for iOS in App.tsx. Should be good for final review.