refactor: take one product's concepts back out of the package

[inureyes]

What

Four places where one product's concepts had come across with the code. Found by re-reading the package against a single question: is this a rendering component, or does it need to know something only a product knows?

Component	What it knew that it should not
DataTable	Where column preferences are stored
ErrorState	That "model" is a kind of error
EmptyState	That a product has Creations, Benchmark and Logs screens
Tabs	A four-name guide vocabulary, half of which lived in the consumer

All four arrived the same way: by lifting product files rather than designing an interface. The sibling @lablup/ui-ai, whose components were written against view models (AiToolCallView, AiRenderAdapters) from the start, has none of them. That difference is the lesson worth keeping.

The four

DataTable wrote to localStorage itself. Where column preferences live, under which key, per user or per workspace, or whether they persist at all, is a decision only a consumer can make. A component that answers it cannot be reused by a consumer that answers differently, and it also stopped the table working anywhere localStorage is absent. persistKey is replaced by columnState + onColumnStateChange. Two new tests: the component touches no storage, and it does not report back the state it was handed, so a caller that persists on change and feeds the result in cannot loop.

ErrorState took an error category. "network" | "configuration" | "model" | "permission" | "generic". Beyond "model" being one product's vocabulary, the five names resolved to three colours: network and permission were the same amber, model and generic the same red. It now takes tone: "danger" | "warning" | "accent" and an optional icon.

EmptyState shipped ten drawings named after one product's screens. No other consumer has a "creations" screen to draw for. illustration is a ReactNode now and the drawings go back to the product that owns those screens. This reverses the export added in 0.1.0-alpha.3, which unblocked that product's migration by widening the wrong side of the boundary. Doing it that way was the expedient move at the time; this is the correct one.

Tabs carried a guide-tag system. That one had already announced itself: TAG_CONFIG kept the badge variant here while the label text had to be passed in through tagLabels from the consumer's locale bundle. A single concept in two repositories is what a wrong boundary looks like from the inside. tag, required, TabTagType, TabTagLabels, TAG_CONFIG and tagLabels are gone; a consumer renders its own badge through the TabItem.labelExtra slot that already existed, and the .tabs__tag-badge class stays so it still looks right.

Breaking

All four. They land while there is exactly one consumer and no stable release, which is the cheapest this will ever be. Migration table is in the changelog.

Verification

pnpm run verify green, including the external install fixture. Packed files 140 to 134.