Fix bundled plugin package metadata

[Fryuni]

Summary

Fix the published bundle so bundled plugin metadata is self-contained instead of resolving a sibling package.json at runtime. This prevents plugins like eslint-plugin-import-x from reading @croct/eslint-plugin's package metadata, or failing when the expected package file is absent.

Changes

• Move eslint-plugin-import-x into runtime dependencies so the package graph matches the bundled code path.
• Add a tsdown/Rolldown plugin that uses the transform AST to inline relative package.json require calls from bundled dependencies.
• Add a regression test that builds the published bundle in an isolated package layout and verifies import-x metadata still points to eslint-plugin-import-x.

Testing

• npm run lint
• npm run validate
• npm test -- --runInBand

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@croct/eslint-plugin@498

commit: 567e808