VACMS - 19549 19800 conditional render services select, and loading indicator until CCP services loaded

[eselkin]

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

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

• Make services render conditionally and add loading indicator until CCP services are loaded
• Sitewide team - we manage the Facility Locator

Related issue(s)

• Conditional Display of Services Selector va.gov-cms#19549
• Loading Animation on FL Community Care Services va.gov-cms#19800

Testing done

• Prior to change, services would always appear for all facilities (including when a facility type was not selected). Make sure it only appears when one is selected. Also when CCP is selected, because of it's dependence on a initial call to PPMS, we make make sure the typeahead only displays when the services have been downloaded. In the interim of CCP selection, show loading indicaor.
• Manually tested

Screenshots

Video with all the options selected on Tablet and Small Desktop and Mobile Sizes

video1572992751.mp4

What areas of the site does it impact?

Facility Locator

Acceptance criteria

#19549

• These Facility Types result in display of "Service type":
  • VA health
  • Urgent care
  • Emergency care
  • Community providers (in VA's network)
• These facility types that NO NOT result in display of "Service type":
  • Community Pharmacies (in VA's network)
  • VA Benefits
  • VA cemeteries
  • Vet Centers
• Ensure that any existing analytics are ported over (no change in analytics)

#19800

• When user selects Community Providers in facility type, the service selector box does not immediately appear
• In its place, a loading animation displays and persists until PPMS data is loaded
• When PPMS data loads, animation is replaced by the services selector

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

Check all conditions on the RI from the video