Core rule gaps: camelcase, spaced-comment, eslint-comments/require-description

[Radiergummi]

Small non-Vue gaps. Verified against the installed oxlint's configuration schema (847 rules):

Rule	In oxlint
id-length	yes
camelcase	no
spaced-comment	no
@eslint-community/eslint-comments/no-unused-disable	see below
@eslint-community/eslint-comments/require-description	no

no-unused-disable is partly covered: oxlint supports reportUnusedDisableDirectives, which overlaps but is not identical.

id-length is already in oxlint, so it can move out of the ESLint base immediately, independent of everything else in this milestone.

What needs to happen

• Move id-length to the oxlint base now. No reason to wait.
• Decide whether camelcase and spaced-comment are worth keeping. spaced-comment in particular exists mainly to permit // region markers, which is a formatting concern oxfmt could own.
• Check whether oxlint's reportUnusedDisableDirectives is a sufficient substitute for no-unused-disable.
• require-description forces a justification on every suppression comment. That is a real code-quality guard with no oxlint equivalent; decide whether to keep it or enforce it by review.