[VACMS-19449]Situation updates static banner

[SnowboardTechie]

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

• Adds a situation updates banner component that when enabled, takes the div prepared by content-build and adds a banner for situation updates. Currently the banner is working with static data and disabled behind a feature flag. Future work will enable this banner on only the appropriate pages (locations with situation updates fetched from vets-api).
• Sitewide team
• This is kept behind the flipper flag banner_use_alternative_banners
• Includes update to watch to setup with 12GB as 8 was not enough to complete builds

Related issue(s)

• Issue: Build the VAMC Banner with Situation Updates in vets-website (Story 2) va.gov-cms#19449
• Epic: [EPIC] VAMC real-time banners that do not use content-build va.gov-cms#19302

Testing done

• This introduces no noticeable changes to users as long as the flipper remains disabled
• When flipper is enabled, it updates the empty situation updates banner with the static data in the property config

Scre

enshots

What areas of the site does it impact?

This is interacting with a header level feature so it has the potential for sitewide impact

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

[eselkin]

Nice use of the feature toggles in the tests.

[eselkin]

Also, thanks for putting in the memory updates for watch. I thought I did, but seemed to have missed it somewhere in my changes.

[randimays]

LGTM!

[eselkin]

LGTM
1 question about common practice/pattern