fix(eslint-plugin): drop conflicting project parser option

The @endo/internal config set both `projectService` and the legacy
`project` glob in parserOptions. typescript-eslint 8.59 now rejects
that combination ("Enabling 'project' does nothing when 'projectService'
is enabled"), so every file failed to parse with a 0:0 error.

Remove the legacy `project: [tsconfig.eslint-full.json]` mechanism (and
its now-unused glob const and redundant `useProjectService` boolean).
The project service supersedes it, discovering the nearest tsconfig per
file and falling back to `defaultProject` for stray `*.js` files.

Verified type-aware linting still engages (restrict-plus-operands fires
on a probe) and packages now lint with 0 errors.

Author: kriskowal

packages/eslint-plugin/lib/configs/internal.js

@@ -5,8 +5,11 @@ const dynamicConfig = {
   overrides: /** @type {*[]} */ ([]),
 };
 
+// The project service discovers the nearest tsconfig per file and falls
+// back to `defaultProject` for stray `*.js` files. It supersedes the older
+// `project` glob, which must not be set alongside it: newer
+// typescript-eslint parsers reject enabling both.
 const parserOptions = {
-  useProjectService: true,
   sourceType: 'module',
   projectService: {
     allowDefaultProject: ['*.js'],