Remove explicit plugin IDs from API builders

[aXenDeveloper]

Summary

• add a shared plugin context that stores the current plugin ID and register it from each plugin's config
• update the module and route builders, core modules, blog plugin modules, and the docs so they infer the plugin ID from the shared context instead of receiving it explicitly

Testing

• pnpm --filter @vitnode/core test
• pnpm --filter @vitnode/core lint (fails: existing @typescript-eslint/no-unsafe-argument violations in views)

---

Codex Task

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vitnode-docs	Error			Nov 16, 2025 10:29am

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "Remove explicit plugin IDs from API builders". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit