chore: fix package.json, add dev tooling, and configure API proxy

[CodingBabe-1]

Summary

This PR addresses Issue #29, fixing developer tooling gaps and improving the developer experience for the EquipChain frontend.

Changes

package.json

• Added npm scripts:
  • format / format:check — Prettier formatting for consistency
  • typecheck — TypeScript type checking (tsc --noEmit)
  • clean — Remove build artifacts (.next and node_modules)
  • analyze — Bundle analysis with ANALYZE=true next build
  • validate — Full validation pipeline: typecheck → lint → build
  • test — Test placeholder (no tests configured yet)
  • storybook / build-storybook — Storybook integration scripts (for future use)
  • gen:api — OpenAPI TypeScript client generation
  • gen:contracts — Soroban contract type generation
  • dev:proxy — Dev server with API proxy (uses concurrently)
  • postinstall — Husky hook setup
• Added devDependencies:
  • concurrently — Run multiple commands in parallel
  • husky — Git hooks for pre-commit validation
  • openapi-typescript — API client type generation
  • prettier — Code formatting
  • tsx — TypeScript execution (for scripts)

next.config.ts

• Added rewrites() configuration to proxy /api/* requests to http://localhost:3001/api/* during development

New Files

• .prettierrc — Prettier configuration (no semicolons, double quotes, trailing commas)
• .nvmrc — Pins Node.js to version 20.x for consistent development environments
• .vscode/launch.json — VS Code debug configurations for Next.js server, client, full-stack, typecheck, and validate
• scripts/generate-contract-types.ts — TypeScript script that reads Soroban contract spec JSON and generates TypeScript type definitions
• scripts/dev-proxy.ts — Scaffold for custom development proxy behavior

Git Hooks

• Set up Husky with a pre-commit hook that runs typecheck and lint before every commit

.gitignore

• Added contract-specs/ to prevent local contract specs from being committed

Verification

All CI checks pass locally:

• ✅ npm install — No warnings or errors
• ✅ npm run typecheck — Zero TypeScript errors
• ✅ npm run lint — Zero ESLint errors or warnings
• ✅ npm run build — Next.js production build succeeds

Closes

Closes #29

Closes #29