Use non-existing example in tests

[RobinMalfait]

This PR makes a small change to the tests. In some cases, where we test @utility functionality we use tab-* utilities.

But there is a possibility that we will add this as an actual utility, so instead let's use a much more generic example-* utility. Then we can read from the --example theme value, and use --resolved-value: …; and --resolved-modifier: …; values.

It's admittedly more vague, but chances of conflicts go way down. Until CSS or Tailwind CSS introduces an example-* utility...

Test plan

1. Only tests changed, and all of them still pass

[greptile-apps]

Confidence Score: 5/5

All changes are confined to test files and are a straight find-and-replace of fixtures; no production code is touched.

Every edit is a mechanical rename of test-only identifiers (tab-* → example-*, tab-size → --resolved-value, theme key renames). The inline snapshots were updated to match, and the one observable output difference (calc expression preserved unevaluated in a custom property vs. a real CSS property) is correct CSS behaviour. No logic, API, or production code changed.

No files require special attention.

_{Reviews (1): Last reviewed commit: "use non-existing example" | Re-trigger Greptile}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: b1f2fa03-d2ec-46a1-97a0-fe1b15630620

📥 Commits

Reviewing files that changed from the base of the PR and between 12eb5ae and b777e7e.

📒 Files selected for processing (3)

• packages/tailwindcss/src/canonicalize-candidates.test.ts
• packages/tailwindcss/src/intellisense.test.ts
• packages/tailwindcss/src/utilities.test.ts

---

Walkthrough

This pull request updates test coverage across three test files for Tailwind CSS functional utilities. The changes systematically replace tab-* fixture utilities with a new example-* utility pattern, refactoring test assertions and snapshots to validate value resolution behavior. Tests are expanded to cover theme variable globbing (--example-* and escaped variants), bare named value canonicalization, arbitrary value syntax, literal values, unsupported data type handling, complex computed expressions with calc, modifier/value pairs, negative utility computation, and default fallback mechanisms. All changes are test-only with no alterations to exported/public entities.

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly describes the main change: replacing test fixtures from tab-* to a non-conflicting example-* utility.
Description check	✅ Passed	The description clearly explains why the change was made (avoid conflicts with potential real utilities) and the test plan confirms all tests pass.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}