feat: enforce V0Error over bare Error in packages/0/src via no-restricted-syntax

[sridhar-3009]

Problem

Closes #248.

PR #247 converted all 8 existing throw new Error(...) sites in packages/0/src to use V0Error with a typed code from V0ErrorDetails. The convention was described in the philosophy but enforced only by author discipline — nothing in CI would catch a future PR landing a bare throw new Error(...).

Fix

Add a no-restricted-syntax block in eslint.config.js scoped to packages/0/src/**/*.ts (with carve-outs for *.test.ts and *.bench.ts):

{
  name: 'vuetify/no-bare-error-throw',
  files: ['packages/0/src/**/*.ts'],
  ignores: ['packages/0/src/**/*.test.ts', 'packages/0/src/**/*.bench.ts'],
  rules: {
    'no-restricted-syntax': ['error',
      {
        selector: 'ThrowStatement > NewExpression[callee.name="Error"]',
        message: 'Use V0Error with a code from V0ErrorDetails instead of bare Error. See packages/0/src/utilities/errors.ts.',
      },
    ],
  },
},

Notes

• Uses no-restricted-syntax — no custom plugin, no new dependency, mirrors the existing withDefaults guard on line 29.
• Re-throws (throw err where err is a caught binding) are not flagged — the selector only matches new Error(...) constructor calls.
• Test and bench files are excluded per the issue spec.
• The rule fires at error severity so it blocks CI on a violation.