VACMS-18444 Facility Locator: add click functionality for mobile map markers

[randimays]

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

• 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

⚠️ TeamSites ⚠️

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

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

Summary

Makes the mobile map markers in Facility Locator clickable. When clicked, the details for the facility should appear below the map and the title of the facility should be focused (yellow outline when screenreader is on).

Related issue(s)

• Link to ticket created in va.gov-team repo
  department-of-veterans-affairs/va.gov-team#0000
• Link to previous change of the code/bug (if applicable)
  department-of-veterans-affairs/vets-website#0000
• Link to epic if not included in ticket
  department-of-veterans-affairs/va.gov-team#0000

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

• 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?

[randimays]

Moved this function to a utility file as it is now shared between ResultsList (used for desktop and the list view on mobile) and SearchResult (used for the single listing on mobile map view)

[randimays]

Moved this code into SearchResult because it is the only place it was being used (for mobile map single listings).

[randimays]

Note that selectedResult is used for whichever facility we're viewing on the Facility Locator detail page (e.g. cemetery or one of the many VBAs that isn't statically-built yet). I couldn't dual-purpose this for the mobile map selected card, unfortunately.

[randimays]

Moved these marker-related utilities to a new utility file (mapMarkers.js)

[randimays]

I moved the switch statement into resultMapper.jsx because now it needs to be shared between the regular results list and the single result shown when a mobile map pin is clicked.