fix: regenerate lavamoat policy for production dependencies

The lavamoat policy was generated against dev node_modules, but the
Docker image installs production-only dependencies (npm ci --only=production),
which have different dependency resolution paths. This caused runtime
errors when running in Docker (e.g., ws requesting "events", get-intrinsic
requesting "es-object-atoms").

Additionally, config.js is loaded dynamically via a computed require in
settings.js, so lavamoat's static analysis never discovered its
dependencies (yargs and its transitive deps). Regenerated the policy
using production node_modules and a shim that statically requires
config.js alongside the main entry point.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: andreabadesso