Chore: Tailwind Migration — AutoApprove Palette

[sachasayan]

Tailwind Migration — AutoApprove Palette

This PR covers the Tailwind Migration to the AutoApprove Palette

It makes no functional changes — this is a straight-port from explicit styles to tailwind utility classes.

Type of Change

• ♻️ Refactor: Code change that neither fixes a bug nor adds a feature.

Pre-Submission Checklist

• Self-Review: I have performed a thorough self-review of my code.
• Code Quality:
  • My code adheres to the project's style guidelines.
  • There are no new linting errors or warnings (npm run lint).
  • All debug code (e.g., console.log) has been removed.
• Testing:
  • New and/or updated tests have been added to cover my changes.
  • All tests pass locally (npm test).
  • The application builds successfully with my changes.
• Branch Hygiene: My branch is up-to-date (rebased) with the main branch.
• Documentation Impact: I have considered if my changes require documentation updates (see "Documentation Updates" section below).
• Changeset: A changeset has been created using npm run changeset if this PR includes user-facing changes or dependency updates.
• Contribution Guidelines: I have read and agree to the Contributor Guidelines.

Screenshots / Videos

No visual impacts, these components look and act identical with the changes applied.

Documentation Updates

Does this PR necessitate updates to user-facing documentation?

• No documentation updates are required.

---

Important

Refactor AutoApproveMenu.tsx to use Tailwind CSS and update index.css with new Tailwind configurations and custom properties.

• Refactor:
  • Migrate styles in AutoApproveMenu.tsx from explicit CSS to Tailwind utility classes.
  • Update index.css with new Tailwind configurations and custom properties for VSCode theme integration.
• CSS Changes:
  • Add custom properties for VSCode colors and fallback colors in index.css.
  • Define new animations and scrollbar styles in index.css.

^{This description was created by for 0af7294. You can customize this summary. It will automatically update as commits are pushed.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0af7294

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[daniel-lxs]

I'll be closing this as stale, we can revisit this migration later and either reopen them or create new PRs.
cc: @mrubens