fix: resolve dev server startup failures (route name conflict + eslint abort)

[Shevon37]

Summary

Two independent bugs currently prevent yarn dev from starting on a fresh clone. Both are reproduced consistently and fixed here.

Bug 1 — Vue Router name conflict (white screen)

src/router/modules/{editor,home,template}.ts declared a child route with the same name as its parent. Vue Router 4 forbids nested routes sharing a name with an ancestor, so createRouter throws at startup and the whole app fails to mount (white screen).

Renamed the child routes to <parent>Index (e.g. editor → editorIndex), matching the convention already used by the syntax/update modules (syntaxHelper, updateLine).

• src/router/modules/editor.ts: child editor → editorIndex
• src/router/modules/home.ts: child home → homeIndex
• src/router/modules/template.ts: child template → templateIndex

Bug 2 — eslint aborts the dev server on first run

vite-plugin-eslint runs with lintOnStart: true, but the auto-generated declaration files auto-imports.d.ts / components.d.ts were not covered by .eslintignore. The prettier formatting error inside the generated file aborts Vite's buildStart and kills the server before it ever starts.

Added auto-imports.d.ts, components.d.ts, and .eslintrc.cjs to both .eslintignore and .prettierignore. (.gitignore already ignores these generated files, so this is the correct scope.)

Test plan

• yarn dev now reaches VITE ready without a route-name error
• yarn dev no longer aborts due to the generated auto-imports.d.ts prettier error
• Route name uniqueness checked across all src/router/modules/* (no duplicates, no parent/child name collisions)

Fixes # (many first-time users hit this on clone)