fix: resolve ESLint & TypeScript issues (replace any catches, remove unused, config fixes)

[MEECHAIN1]

Motivation

• Eliminate ESLint @typescript-eslint/no-explicit-any and related TypeScript complaints by making error handling safe and removing unused or permissive types.
• Fix lint/format complaints caused by empty interfaces, unused imports/args, and forbidden require() usage in configuration files.

Description

• Replaced unsafe catch (err: any) bindings with catch (err: unknown) and use err instanceof Error ? err.message : <fallback> across RPC proxy, Live panel, Magic views, JSON-RPC terminal, Stats monitor, Verification runner, and page fetch logic.
• Removed or simplified unused symbols and props (unused icon imports, unused chaosMode param renamed to _chaosMode), and converted empty UI prop interfaces into type aliases for InputProps, TextareaProps, and CommandDialogProps to satisfy @typescript-eslint/no-empty-object-type.
• Adjusted parsing/initialization in JsonRpcTerminal to avoid unnecessary initial assignments for parsedParams.
• Declared CommonJS globals in next.config.js/postcss.config.js and replaced Tailwind require('tailwindcss-animate') with an ESM import import tailwindcssAnimate from 'tailwindcss-animate' in tailwind.config.ts.
• Minor robustness fixes in ProductionCodeHub error handling and other small cleanups to address ESLint warnings.

Testing

• Ran npm run lint and linting passed after the changes.
• Ran npm run typecheck (tsc --noEmit) and TypeScript checks passed.
• Built the app with npm run build and the Next.js production build completed successfully.

---

Codex Task

[MEECHAIN1]

Nice 👍