Suppress misleading 'async daemon is disabled' warning under Wolverine-managed event subscription distribution (#3290)

[jeremydmiller]

Closes #3290

Root cause

Marten's DocumentStore constructor writes this console warning whenever async projections are registered but StoreOptions.Projections.AsyncMode == DaemonMode.Disabled:

Warning: The async daemon is disabled.
Projections ... will not be executed without the async daemon enabled

UseWolverineManagedEventSubscriptionDistribution = true deliberately replaces Marten's AddAsyncDaemon(DaemonMode.HotCold) registration with WolverineProjectionCoordinator — but Marten's only knowledge of the daemon state is Projections.AsyncMode, which the integration never set. So it stayed Disabled, the warning fired for every store, and it was flatly wrong: the async projections DO run under Wolverine's managed distribution.

Fix

MartenOverrides — the IConfigureMarten hook the integration already registers for the main store and (via MartenOverrides<T>) every ancillary store — now records the real daemon state: when the resolved MartenIntegration has UseWolverineManagedEventSubscriptionDistribution enabled and AsyncMode is still Disabled, it sets AsyncMode = DaemonMode.HotCold, exactly what the AddAsyncDaemon(HotCold) call it replaces would have recorded.

Deliberately narrow:

• Only upgrades from Disabled — an explicit user AddAsyncDaemon() choice is never overwritten (regardless of call order relative to IntegrateWithWolverine).
• Projections.AsyncMode is purely descriptive here: Marten's own ProjectionCoordinator hosted service is only registered by AddAsyncDaemon() itself, so no Marten-side daemon gets started by this — the only Marten readers of the value are the warning gate and the coordinator Mode properties.
• Stores without managed distribution warn exactly as before.

Tests

Bug_3290_misleading_daemon_disabled_warning (MartenTests) captures Console.Out around DocumentStore construction (the warning is a Console.WriteLine, not ILogger) and asserts:

• managed distribution → AsyncMode == HotCold, no "The async daemon is disabled" output
• no managed distribution → AsyncMode == Disabled, warning still emitted (behavior preserved)
• managed distribution + explicit AddAsyncDaemon(Solo) → stays Solo

Verified locally: new tests green on net9.0 + net10.0; MartenTests.Distribution suite (26 tests — the managed-distribution mechanics that now see HotCold) and AncillaryStores suite (19 tests) green on net10.0.

🤖 Generated with Claude Code

[jeremydmiller]

Closing per review: setting AsyncMode = HotCold from the integration is wrong — it records a mode that turns Marten's own daemon coordination on in parallel with Wolverine's managed distribution.

Correct design instead: a fourth DaemonMode enum value, ExternallyManaged — no warnings from the store, no store-hosted coordination, and Wolverine's MartenIntegration sets it explicitly (same for the Polecat integration, which most likely has the same issue). Chain: JasperFx enum + core handling → Marten (warning gate + coordinator registration) → Wolverine integration sets it → Polecat parity. The test coverage from this PR (console capture, explicit-user-choice preservation) carries into the redo. Tracked under JasperFx/jasperfx#486 / wolverine#3290.

🤖 Generated with Claude Code