15308 Update color variables in CSS

[edmund-dunn]

Description

Relates to #15308

Testing done

Screenshots

QA steps

What needs to be checked to prove this works?
What needs to be checked to prove it didn't break any related things?
What variations of circumstances (users, actions, values) need to be checked?

Review colors and a11y per #15309

Definition of Done

• Documentation has been updated, if applicable.
• Tests have been added if necessary.
• Automated tests have passed.
• Code Quality Tests have passed.
• Acceptance Criteria in related issue are met.
• Manual Code Review Approved.

Select Team for PR review

• CMS Team
• Public websites
• Facilities
• User support
• Accelerated Publishing

Is this PR blocked by another PR?

• DO NOT MERGE

Does this PR need review from a Product Owner

• Needs PO review

CMS user-facing announcement

Is an announcement needed to let editors know of this change?

• Yes, and it's written in issue ____ and queued for publication.
  • Merge and ping the UX writer so they are ready to publish after deployment
• Yes, but it hasn't yet been written
  • Don't merge yet -- ping the UX writer to write and queue content
• No announcement is needed for this code change.
  • Merge & carry on unburdened by announcements

[laflannery]

I'm tested quite a few pages and no color contrast issues are being flagged so this looks good to me.

[ndouglas]

@edmund-dunn Any particular reason this hasn't been merged yet? 🤔

[BlakeOrgan]

@ndouglas I am reviewing this as part of #15309 before merging.

[gracekretschmer-metrostar]

Pull up for sprint 22 and bring in Amanda and Marisa.

[JakeBapple]

Strategy:
new branch from main using 15308 naming
merge in 15308 and then 14753
run the storybook styles and then the theme command to check for errors
tag edmund, steve, and marissa for review
can close those two after we merge in the new one

[JakeBapple]

closing this pr as it was consolidated in this: #19520