BUG - Add testID option to segmented control component

[rbontrager]

What happened?

Some of our detox tests are currently failing because the tests were looking for a id from the old testID function. This was cleaned up and removed when the segment control component was made. While we can change the tests to look for the text for now it would be nice to have a testID option added back in so we don't have any flakiness in the future.

Specs:

• Device:
• OS:
• User Account:
• Accessibility State:

Steps to Reproduce

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

• Impact: High Low
• Frequency: High Low

• 3 - Low
• 2 - High
• 1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

• Steps to reproduce are defined
• Desired behavior is added
• Labels added (front-end, back-end, relevant feature, accessibility, etc)
• Estimate of 1 added (for front-end tickets)
• Added either to the relevant feature epic (if found during new feature implementation), or the bug epic

[narin]

PR created: department-of-veterans-affairs/va-mobile-library#19

[narin]

Code is complete and merged in MoVADS repo. Waiting on va-mobile-app PR review to bump the version on the app: #6886

[narin]

@rbontrager Can we consider this ticket complete, or were you expecting for testIDs to be added to each existing SegmentedControl as part of this work?

[rbontrager]

Verified that testIDs have been added to segmented control.