[Feature] Update Icon component for new Icons

[narin]

Description of Change

• Bumps mobile-assets to 0.12.0 in component package.json
• Ran yarn buildIcons to rebuild Icon list and update imports in Icon component

Testing Packages

• assets@0.11.1-alpha.0

Screenshots/Video

Web

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/1742197c-f0f2-4b0c-983a-b92c1a357a23

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/2e10d426-c7b5-4793-bdca-a265f055d37f

iOS

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/af516908-4db7-4232-8356-e351ddf5244f

Android

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/786704/d482e625-0ccf-400b-b93f-dddb1a810e0c

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:

• [ ] Merge main into branch
• [ ] Merge branch to main
• [ ] Verify that Check Component Integrations workflow ran successfully
• [ ] Publish new version after merging