POC - Semantic Token upgrade approach

[megrenn]

To successfully achieve our goal of launching Dual Branding (theming) across ecommerce digital experiences, we need to follow two strategies: 1. New development utilizes semantic theming tokens and 2. Legacy development is upgraded to semantic theming tokens.

This Spike is to determine the feasibility of a script (or script) that will:

• crawl through existing code and identify use of Auro Components which are out of date enough that they don't support theming
• Look for hard coded colors (prioritize more common ways that colors are defined)
• When a hard coded color is found, comment the potential design tokens it could be replaced with to enable theming

It currently does not seem feasible to automatically make updates to the relevant code, since it will be impossible in many cases to determine which token is appropriate. The basic idea is to use the script like a pseudo-linter for theming.

For whatever we have deemed feasible above, we also want to assess:

• What is the benefit for other teams in having these theming gaps identified
• What do we foresee as the potential time save for teams (roughly)
• Will this minimize the chance of us needing to innersource (or the time spent innersourcing)
• Can this be used to help us judge theme readiness across the org?

[megrenn]

@jason-capsule42 wasn't sure which Repo to put this in since it's general Auro implementation across the board; so please update as necessary

[Patrick-Daly-AA]

Put in big update to the description based off of today's refinement.