feat: check module activation in pollora:doctor and add pollora:module:frontend

[ogorzalka]

Step 7 of the modules specification, framework part (docs and Nectar follow in their own repositories).

What changes

• module-activation check (pollora:doctor and Site Health), warnings for:
  • the database connector reading its fallback (options table unreadable);
  • a module the connector lists but the disk no longer has;
  • a state file that cannot be written while Plugins › Modules is the way to switch (MODULES_ADMIN_TOGGLE on);
  • a configuration or route cache older than the last switch (JSON connector: compared with the file's modification time);
  • MODULES_CONNECTOR / MODULES_LOCKED_* / MODULES_ENABLED|DISABLED set while config/modules.php is not published — nwidart reads its activator before any provider, so they are ignored (the trap found in step 4).
• Builds check: recognises the Vite config of nwidart's stock module:make (buildDirectory: 'build-<lower>') and points to the command below.
• pollora:module:frontend Crm: writes package.json, vite.config.js (on @pollora/vite-config) and resources/assets/app.{js,css} from the bundled module template, keeping a .bak of each replaced file (--no-backup). No automatic migration at upgrade.
• E2E: the Site Health spec expects the "Module activation" label.

Independent of #438/#439 (based on develop).

Tests

Pest: ModuleDoctorTest (each warning, the passing case, the command with backup, unknown module) and the stock-config case in ModuleChecksTest. Full suite 1941 passed; PHPStan, Rector, Pint, type coverage clean.