MHV-62687 SM: optgroups for recipients TG select dropdown UPDATED

[oleksii-morgun]

Note: Delete the description statements, complete each step. None are optional, but can be justified as to why they cannot be completed as written. Provide known gaps to testing that may raise the risk of merging to production.

Are you removing, renaming or moving a folder in this PR?

• [x] No, I'm not changing any folders (skip to TeamSites and delete the rest of this section)
• [ ] Yes, I'm removing, renaming or moving a folder

:warning: TeamSites :warning:

Examples of a TeamSite: https://va.gov/health and https://benefits.va.gov/benefits/. This scenario is also referred to as the "injected" header and footer. You can reach out in the #sitewide-public-websites Slack channel for questions.

Did you change site-wide styles, platform utilities or other infrastructure?

• [x] No
• [ ] Yes, and I used the proxy-rewrite steps to test the injected header scenario

Summary

• adding optgroups to recipient select dropdown on my-health/new-message page
• triage teams are grouped by facility and optgroups represented by a facility name
• behind the feature flag mhv_secure_messaging_recipient_opt_groups

Related issue(s)

• MHV-62687
• https://www.figma.com/design/JYvOPQ0HpdlDVgTt2WGx0S/Plain-Language-Care-Team-Names-(Triage-group)-naming?node-id=436-3809

Testing done

• Describe what the old behavior was prior to the change
• Describe the steps required to verify your changes are working as expected
• Describe the tests completed and the results
• _Exclusively stating 'Specs and automated tests passing' is NOT acceptable as appropriate testing
• Optionally, provide a link to your test plan and test execution records

Screenshots

Note: This field is mandatory for UI changes (non-component work should NOT have screenshots).

	Before	After
Mobile
Desktop

What areas of the site does it impact?

(Describe what parts of the site are impacted if code touched other areas)

Acceptance criteria

Quality Assurance & Testing

• [ ] I fixed|updated|added unit tests and integration tests for each feature (if applicable).
• [x] No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
• [ ] Linting warnings have been addressed
• [ ] Documentation has been updated (link to documentation *if necessary)
• [x] Screenshot of the developed feature is added
• [ ] Accessibility testing has been performed

Error Handling

• [ ] Browser console contains no warnings or errors.
• [ ] Events are being sent to the appropriate logging solution
• [ ] Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

• [x] Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

(OPTIONAL) What should the reviewers know in addition to the above. Is there anything specific you wish the reviewer to assist with. Do you have any concerns with this PR, why?