fix(codemods): codemods for two entries the catalogue called manual

[mfal]

Two published catalogue entries said action: manual while their change is
mechanically decidable. Both corrections were reported from the same real
upgrade run, and both are extracted from #3041 — that PR targets
next for its package-manager work, but a codemod for a migration that is
already in main is a fix to a published entry, not a feature.

renamed-css-export

Same shape as password-tools-subpath-renamed, which ships a codemod: one exact
module specifier, swapped. Two entries with the same shape and different
action values is hard to explain to a reader budgeting manual review.

Modelled on that neighbour — every JS/TS form that names a module, exact match
rather than prefix, since ./styles had nothing underneath it (all-layered.css
beside it stays untouched). It cannot reach an @import in a .css/.scss, and
apply says so rather than implying full coverage.

catalog.test.ts used renamed-css-export as its example of a manual entry, so
adding the codemod broke a test that was only ever checking that the parser reads
a non-codemod action. Made it id-independent; the correspondence between
action and the transform file is enforced separately, over every entry.

table-column-width-props

Follows the accent-box-color-to-background-color template: a codemod for the
decidable subset, with apply naming what it will not touch.

• maxWidth always goes. The prop was removed from the type, so an explicit
  attribute is wrong at any value, maxWidth={computed} included.
• width/minWidth go only where the source literally says null.
  width={maybeNull} could be anything at runtime and is left alone, exactly as
  accent-box-color-to-background-color leaves color={expression}.

Scoped like its neighbours: only elements resolving to TableColumn through a
Flow import — named, aliased or namespace, subpath entries included. A spread
that might carry maxWidth is invisible and stays. apply names both gaps.

Verification

• 301 unit tests pass (16 of them the two new fixture files), test:compile
  clean, pnpm lint clean (0 errors, prettier green)
• pnpm nx build codemods regenerates nothing further — MIGRATION.md and
  migrations.generated.ts in this branch are current

Follow-up

#3041 still carries these two commits. Once this merges, that PR
should drop them; what remains there is the package-manager install work, which
stays a feat on next.

fixes #3061

🤖 Generated with Claude Code

[github-actions]

Coverage Report for ./packages/components/

Status	Category	Percentage	Covered / Total
🔵	Lines	78.69%	746 / 948
🔵	Statements	78.57%	763 / 971
🔵	Functions	80.09%	165 / 206
🔵	Branches	70.33%	377 / 536

File Coverage

No changed files found.

Generated in workflow #6618 for commit 099de7c by the Vitest Coverage Report Action

[github-actions]

🚀 Preview Deployment

Preview environments are ready:

Type	URL
docs	pr-3047.docs.review.flow-components.de
storybook	pr-3047.storybook.review.flow-components.de

Images:

• docs: ghcr.io/mittwald/flow/docs:pr-3047
• storybook: ghcr.io/mittwald/flow/storybook:pr-3047