Story-1676 pramaan-admin dependency cleanup

Admin removes the final nuqs scaffolding

The previous stories removed runtime URL-state usage. This chore removes the now-dead adapters, test wrappers, dependency entry, and stale source text without changing list behavior.

What changed

The root app layout now renders Clerk, page children, tracing UI, and toast UI directly without the global adapter mount. The firms client now renders the already-migrated list content directly without the browser adapter wrapper.

src/app/layout.tsx no longer imports or mounts NuqsAdapter.
src/app/(admin)/firms/firms-client.tsx no longer imports or mounts BrowserNuqsAdapter.
The surviving firms, staff, and support-access stories render their components directly inside the existing React Query provider.
The unit tests that previously carried the testing adapter now rely on the same browser-history helpers used by the migrated code path.

Dependency proof

nuqs was removed from package.json, and pnpm-lock.yaml no longer contains its importer entry, package block, or snapshot. A clean pnpm install removes it from the installed dependency set.

Scope guardrails

No list logic, use-data-table.ts, migrated table behavior, useReactTable usage, generated contracts, backend code, pramaan-app files, or i18n plumbing changed.

pramaan-docs ADR-124: dependency and cleanup only; instrumentation-exempt.

Verification proof

Required absence checks: grep -rn "nuqs" src returns no output, and grep -rn "nuqs" package.json pnpm-lock.yaml returns no output.

Required local verification: pnpm install, pnpm lint, pnpm exec tsc --noEmit, pnpm test, NEXT_PUBLIC_ENV=local pnpm build, pnpm build-storybook, and git diff --check.