Update TypeScript and ESLint configs for compatibility

[mcous]

Overview

This PR makes some changes in reaction to integrating these configs into viamrobotics/prime.

1. Change how @viamrobotics/typescript-config specifies exports
2. Fix some ESLint rules in reaction to how we actually write code
3. Prevent internal tsconfig.json files from being published in the modules

I tested these changes locally with Prime.

Changelog

TypeScript

Lesson no. 1 from integrating the common configs into a project: the TypeScript config world is not yet ready for packageJson.exports. Support in tsc itself is barely there in v5 (e.g. see microsoft/TypeScript#53314), and other related tooling - like get-tsconfig, used in eslint-plugin-import - completely chokes on it.

This PR updates the TypeScript config package to remove exports, so package consumers can specify file paths directly, and updates the documentation. It's less neat, but more pragmatic.

{
  // before
  "extends": "@viamrobotics/typescript-config"
  
  // after
  "extends": "@viamrobotics/typescript-config/base.json"
}

ESLint

• Remove no-duplicate-imports, it's redundant with the already enabled import/no-duplicates and is annoying about type imports
• Replace no-use-before-define with type-aware @typescript-eslint/no-use-before-define and configure to only catch actual errors
  • The default configuration triggers annoying false positives for stuff like...

  const handleEvent = () => {
    cleanup()  // <- works because cleanup is in a higher scope, but no-use-before-define complains
    console.log('event!')
  }
  
  const cleanup = () => {
    emitter.off('event', handleEvent)
  }
  
  emitter.on('event', handleEvent)

[DTCurrie]

✅