Fix CI breakage for ESLint 10 dependency bump

[Copilot]

The ESLint 10 Dependabot update broke CI before any job-specific work ran, and it also exposed an incompatibility in the repo’s flat ESLint setup for root config files. This PR updates the repo metadata and lint config so the dependency bump can run through the existing workflow again.

• CI setup

  • Remove the stale Yarn release path from .yarnrc.yml so Node/npm setup no longer fails on a missing .yarn/releases/yarn-4.11.0.cjs.
  • Keep a valid packageManager in package.json, but point it at npm so Turbo can still resolve tasks in CI.

• Dependency metadata

  • Sync package-lock.json with the bumped eslint / @eslint/js versions so npm ci matches package.json.

• ESLint 10 compatibility

  • Scope the React Native legacy ESLint config to the TypeScript source tree instead of applying it to every *.js file in the repo.
  • Add explicit handling for root *.js and *.mjs config files using @eslint/js recommended rules plus the existing Prettier rule.

• Config shape

  • The effective change is narrowing the legacy config and linting repo-level config files separately:

export default defineConfig([
  {
    files: ['src/**/*.{ts,tsx}'],
    extends: fixupConfigRules(compat.extends('@react-native', 'prettier')),
  },
  {
    ...js.configs.recommended,
    files: ['*.js'],
    languageOptions: { sourceType: 'commonjs' },
  },
  {
    ...js.configs.recommended,
    files: ['*.mjs'],
  },
]);

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.