feat: Enable dark mode toggle

[gidjin]

SC-1248

Proposed changes

This PR replaces #839 and merges in the developer work flow improvements. It also enables the

• Fix sysinfo so that git sha aka BUILD_ID is displayed
• Add way to run portal in docker mimicking deployed environments
• Minor improvements to our docker compose configuration
  • These are also the reason this USSF-ORBIT/ussf-portal-cms#204 was created as well
• Enable Theme Toggle on all pages
• Remove Launch Darkly configuration
• Fix CODEOWNERS configuration

Reviewer notes

• Make sure ThemeToggle button is working via normal development process (aka yarn dev)
• Make sure everything appears to work in docker container. Run yarn portal:up See also updated docs in development.md file
• Review changes in development.md

Reviewer notes

Per our discussions we are aiming to release DarkMode at the end of the iteration. This pr does that and removes the launch darkly stuff.

Setup

Typical yarn services:up and yarn dev in cms and client repos

Code review steps

As the original developer, I have

• Met the acceptance criteria, or will meet them in subsequent PRs or stories
  • ...
• Created new stories in Storybook if applicable
  • Checked that all Storybook accessibility checks are passing
• Created/modified automated unit tests in Jest
  • Including jest-axe checks when UI changes
• Created/modified automated E2E tests in Cypress
  • Including cypress-axe checks when UI changes
  • Checked that the E2E test build is not failing
• Performed a11y testing:
  • Checked responsiveness in mobile, tablet, and desktop
  • Checked keyboard navigability
  • Tested with VoiceOver in Safari
  • Checked VO's rotor menu for landmarks, page heading structure and links
  • Used a browser a11y tool to check for issues (WAVE, axe, ANDI or Accessibility addon tab for Storybook)
• Requested a design review for user-facing changes
• For any new migrations/schema changes:
  • Followed guidelines for zero-downtime deploys

As code reviewer(s), I have

• Pulled this branch locally and tested it
• Reviewed this code and left comments
• Checked that all code is adequately covered by tests
  • Checked that the E2E test build is not failing
• Made it clear which comments need to be addressed before this work is merged
• Considered marking this as accepted even if there are small changes needed
• Performed a11y testing:
  • Checked responsiveness in mobile, tablet, and desktop
  • Checked keyboard navigability
  • Tested with VoiceOver in Safari
  • Checked VO's rotor menu for landmarks, page heading structure and links
  • Used a browser a11y tool to check for issues (WAVE, axe, ANDI or Accessibility addon tab for Storybook)

As a designer reviewer, I have

• Checked in the design translated visually
• Checked behavior
• Checked different states (empty, one, some, error)
• Checked for landmarks, page heading structure, and links
• Tried to break the intended flow
• Performed a11y testing:
  • Checked responsiveness in mobile, tablet, and desktop
  • Checked keyboard navigability
  • Tested with VoiceOver in Safari
  • Checked VO's rotor menu for landmarks, page heading structure and links
  • Used a browser a11y tool to check for issues (WAVE, axe, ANDI or Accessibility addon tab for Storybook)

As a test user, I have

• Run through the Test Script:
  • On commercial internet in IE11
  • On commercial internet in Firefox
  • On commercial internet in Chrome
  • On commercial internet in Safari
  • On NIPR in IE11
  • On NIPR in Firefox
  • On NIPR in Chrome
  • On NIPR in Safari
  • On a mobile device in Firefox
  • On a mobile device in Chrome
  • On a mobile device in Safari
• Added any anomalous behavior to this PR

---

Screenshots

[shortcut-integration]

This pull request has been linked to Shortcut Story #1248: Launch darkly client id is not loading at run time.

[malworks]

Only looked at the visuals (toggle theme on all pages) but looks good to me!

[jcbcapps]

Looks great! I left one question, but I don't think it's blocking. I also ran e2e tests locally and they were all passing for me, so not sure why they keep failing here.

[jcbcapps]

Does 'e2e-local' need to be hard coded here?

[gidjin]

Good question. I think it's okay here since we only ever use the docker-compose.cms.yml when running things locally in docker via yarn cms:up. If we started using this docker compose file elsewhere we would want to consider changing it like in USSF-ORBIT/ussf-portal#163. That PR is different since the E2E workflow uses docker compose to start up all the various services.