[Feature] Create Link Component

[TimRoe]

Description of Change

• Created the core of the Link Component
  • Split off:
    • Adding in-line link variant to #168
    • Native bridge for adding to calendar to #169
    • Adding analytics passthroughs to #170
    • iOS Storybook press style bug to #171 (only manifests in Storybook iOS, works in Web/Android Storybook and in flagship in both iOS and Android
  • Link component supports:
    • 7 types of links: calendar, call, call TTY, custom, directions, text, url
      • Each with typescript enforced corresponding data
    • Text to display with optional a11yLabel and a11yHints to better support screen reader users
    • 2 color variants: default (primary blue) and base (gray to distinguish contrast)
    • Icon override if desired: including both removing icon and setting to a custom icon with full icon props to override anything
    • onPress logic override if desired; required for custom type link as not a handled default
    • Prompt text override: for directions and url types, ability to override all text shown in the prompt that appears (title, body, confirm, cancel)
    • testID to support unit test suites
• Known issue besides the above split offs:
  • Needs ticket #165 for dark mode base variant icons to not be a severe contrast violation
  • Ticket #172 will rework how the directions type will prompt user interaction before leaving
• Created new OSfunctions utilities set
  • Utility for building up a directions URL from location data
  • Utility for handling an external link leaving the app
  • Tentative utility for adding an event to calendar, but non-functional to be addressed with #169
• Created basic Storybook stories solely for testing
  • Ticket #135 outstanding to hash out with design what all we want to demonstrate

Testing Packages

• 0.5.2-alpha.2
• 0.5.2-alpha.1
• 0.5.2-alpha.0

Screenshots/Video

Android Storybook:

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/8690976/811fe130-27d1-4a78-bae7-22ea94b80a18

Android Flagship:

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/8690976/d915b5ba-adbe-46b8-b494-2cb4c10459c8

iOS Flagship:

https://github.com/department-of-veterans-affairs/va-mobile-library/assets/8690976/45731c36-1cc4-4f2c-a729-384dc1ea3ccd

Testing

Draft tested around in all 3 Storybook versions as well as iOS/Android in the app with alpha build replacing a handful of links of various varieties.

• [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)

    • 134

  • [x] New functions have proper TSDoc annotations

Publish

While changes warrant a new version per the versioning guidelines, the component's state is rough and it is deemed wise to await subsequent tickets to publish a version officially releasing it.