fix enrich: use SEQUENTIAL execution to avoid DuckDB lock conflicts
PER_NODE runs seed + model tasks concurrently; DuckDB only allows one
writer at a time, causing "Conflicting lock" errors on the shared
/prefect-analytics/analytics.duckdb hostPath file.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>