fix(desktop): load Tailwind's stylesheet first so its layer order holds
The 1.30.2 canary built at ef00bb7db rendered with most Tailwind utilities
losing to preflight: padding, gaps, borders and popover positioning all
collapsed. #7869 gave dashboardSidebarLocal/schema.ts a value import from
the @superset/panes barrel, which pulled panes' TabBar into the entry graph.
Its JS was tree-shaken, but OverflowFadeText's import "../fade-edge.css"
survived as a side effect, and landed in the entry stylesheet ahead of
globals.css. fade-edge.css wraps its rules in @layer utilities, so the
utilities layer was declared first — the lowest priority — and Tailwind's
base layer beat every utility.
Importing globals.css before anything else makes Tailwind's layer order the
first thing the entry stylesheet declares, whatever layered CSS a later
import drags into the entry chunk.
Verified: a production renderer build now emits properties, theme, base,
components, utilities before the fade-edge block (the canary's index CSS
opened with @layer utilities); the dev app over CDP renders the sidebar
and new-workspace view with utilities applied.
Summary by cubic
Fixes the desktop renderer's CSS layer order so Tailwind utilities stop losing to preflight.
The 1.30.2 canary rendered with padding, gaps, borders, and popover positioning collapsed after #7869 pulled fade-edge.css into the entry stylesheet ahead of globals.css. Since fade-edge.css declares @layer utilities first, Tailwind's base layer outranked every utility.
Importing globals.css and the bundled fonts at the very top of index.tsx ensures Tailwind's layer order (properties, theme, base, components, utilities) is declared before any layered CSS later imports drag in. Verified via a production renderer build and the dev app over CDP.