feat(windows): automatic configuration generation for npm start and npm server

Description

Currently, the .pilotdeck directory and related configuration files are only generated by the predev hook when running npm run dev.

If users launch the app with npm run start or npm run server inside the ui directory, the bootstrap-pilotdeck-config.mjs script will not execute. This causes startup failures on Windows due to missing directories and config files.

Proposed Solution

1. Add prestart and preserver hooks in ui/package.json to run the bootstrap script before executing corresponding commands.
2. (Optional but recommended) Add auto-bootstrap logic in entry files like load-env.js as a fallback. It guarantees environment initialization no matter which startup command is used.

Additional Context

This issue is closely related to the Windows compatibility fix in #28. Automating the configuration process will greatly reduce the onboarding difficulty for new Windows users.

Start with ui/package.json and the bootstrap-pilotdeck-config.mjs script to see how the existing predev hook initializes configuration. Check load-env.js for the optional fallback, then verify that npm start and npm server execute the bootstrap before startup, including on Windows.