[Feature] Add assets package, Icon component, and reference files from component library

[narin]

Ticket department-of-veterans-affairs/va-mobile-app#50

Description of Change

Creates a new package called mobile-assets that houses our static files such as fonts and SVGs.

• assets package does not contain any code. It is up to the consuming app to import/transform as needed
• Updated components to import fonts from assets repo
• Note: Loading fonts from an node module seems to work fine on iOS but is broken on Android. For this reason I've left the fonts in the components repo. Bug ticket to investigate further created here: https://github.com/department-of-veterans-affairs/va-mobile-library/issues/98
• Updated storybook web to copy fonts from assets library to web server static folder
• Updated components to support loading of SVG assets using react-native-svg-transformer
• Created Icon component and barebones story and unit tests
• Tested in mobile app by replacing VAIcon with Icon on login screen for VA logo and carat next to "Find a VA location" (Screenshot below)
• Created app propagation ticket

Testing Packages

• assets-v0.1.0-alpha.0
• components-v0.3.6-alpha.9
• components-v0.3.6-alpha.10
• components-v0.3.6-alpha.11
• components-v0.3.6-alpha.12

Screenshots/Video

iOS fonts

Web

iOS Icon

Web Icon

VA Mobile App test

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]

Could potentially be split to a separate ticket as this is already large, but did this AC get tested?

Test within VA mobile app that fonts and icons can be consumed

Assuming not with the lack of a components package alpha publish.

Also, this AC needs a ticket created:

Create separate ticket for flagship to update over to leveraging the assets package for fonts/SVGs

[TimRoe]

Somewhat against process, but should we publish assets 0.1.0 on this branch? If not, I think we'll need another PR to update components to use the right package before publishing components 0.4.0.

[narin]

Tested in the mobile app, added screenshots, created propagation ticket, resolved all suggestion or created tickets. Ready for another review.