runtime: enforce per-module resource limits and local-store quota

[mfw78]

Resource limits are configurable at the engine level via [limits] (fuel_per_event, memory_bytes, defaults 1B instructions / 64 MiB) but are global, not per-module, and the manifest parser has no resource fields. On the storage side, all modules share a single redb Database and set() does no size accounting, so a single module can write unbounded keys/values and exhaust disk for all modules. Fix: per-module limit overrides and a per-module local-store quota.

File: crates/nexum-engine/src/supervisor.rs

[mfw78]

Scope widens from per-module to per-component: venue adapters and analyzers get the same treatment (doc 09, PR #132; see #137/#139).