Description

This PR addresses the need to refine our linting process by excluding specific files from the 'color-no-hex' rule, as outlined in Issue #23097. The motivation behind this change is to prevent lint warning blindness among developers by focusing on meaningful lint warnings that are relevant to the main application. By updating our lint configuration to ignore certain files where static hex color values are permissible, we aim to maintain the effectiveness of our linting process while acknowledging the unique requirements of standalone or external parts of our project.

Improvement/Solution

• Updated the lint configuration to exclude specific files from the 'color-no-hex' rule.
• Identified files where static hex color values are permissible due to their standalone nature or external usage.

Related issues

Fixes: #23097

Manual testing steps

1. Pull this branch
2. Run yarn lint
3. Notice that there shouldn't be any static hex value warnings from stylelint

Screenshots/Recordings

Before

Below screencast shows warnings that should be ignored

After

Below screencast shows no more stylelint warnings for static hex

Linting still works as intended for other files

Pre-merge author checklist

• I’ve followed MetaMask Coding Standards.
• I've clearly explained what problem this PR is solving and how it is solved.
• I've linked related issues.
• I've included manual testing steps.
• I’ve included tests if applicable.
• I’ve documented my code using JSDoc format if applicable.
• I’ve applied the right labels on the PR.
• I’ve properly set the pull request status to "ready for review".

Pre-merge reviewer checklist

• I've manually tested the PR (e.g., pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the issue it closes and includes the necessary testing evidence.

This PR template is filled out with a concise description of the changes, the motivation behind them, and the solution provided. It also includes a link to the related issue, outlines the manual testing steps, and adheres to the pre-merge checklists for both the author and the reviewer.