Update color tokens for theming support

[jordanjones243]

General Support Request

In order to make Auro components themeable, we need to make sure there are no hard-coded and correct semanticly named tokens within the component. There also needs to be investigation around border rules which have a combination of size and color tokens, making them more complex, as well as background-color and color rules.

Possible Solution

Work with designers to figure out what tokens need updated values or renamed.

Additional context

This work stems from theming work happening to all Auro components:

• https://github.com/AlaskaAirlines/AuroDesignTokens/issues/147

Rules and tokens to be edited can be found in the comments.

Acceptance Criteria:

• [ ] All tier 3 token names have been implemented.
• [ ] Colors identified below have been updated to their tier 3 token name.

[jordanjones243]

• Hardcoded
  • Drawer overlay —open:
    • Background: rgba(0, 0, 0, 0.2);
  • Drawer overlay —modal:
    • Background: rgba(0, 0, 0, 0.5);
  • box-shadow: 0 10px 20px 0 rgba(0,0,0,0.12), 0 1px 10px 0 rgba(0,0,0,0.1);
  • Transparent
• Tier 1
  • Unformatted ondark dialog header action color: var(--ds-color-base-white, $ds-color-base-white);

[jordanjones243]

This ticket will be blocked until this work is completed:

• https://github.com/AlaskaAirlines/auro-button/issues/252

[jordanjones243]

Blocked by auro-button color theming support release.

[jordanjones243]

Need design to revise the semantic tokens being used within the tokens.scss file.