Component and UI color changes post accessible palette update
## Background
In https://gitlab.com/gitlab-org/gitlab-ui/-/issues/627, work was done to update the primary palette and themes to be more accessible, and to normalize the color steps across hues so that everything from component variants and states uses predictable color variables.
Generally speaking, several colors in use today do not meet the necessary 4.5:1 contrast ratio against a background color per the [WCAG 2.1 1.4.3 AA guidelines](https://www.w3.org/TR/WCAG21/#contrast-minimum), and have to be darkened to do so in https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/1099.
## Problem
After https://gitlab.com/gitlab-org/gitlab-ui/-/merge_requests/1099 was completed there are many components and UI elements where color assignments (which variables or CSS classes are used) need updated. The scope of this epic is to identify components and UI that require updates, and capture each in an issue so that they can be addressed.
The primary impact is to the orange and neutral palettes. Orange and green hues have a tougher time meeting the contrast requirements, and as a result, have to be darker than often desired.
## Solution
The primary focus will be to:
* Update variables in GitLab SCSS to align with new color assignments in gitlab-ui SCSS
* Ensure that components and UI elements are using the correct colors, as represented in [Pajamas](https://design.gitlab.com/) design specs
* Capture issues where current color use in the product should be reconsidered
* Explore ways to provide meaning and context that do not rely on color alone
/cc @gitlab-com/gitlab-ux/designers @ealcantara
epic