AML support: profile mod + conditional --mod-manager launch flag

[ModifAmorphic]

Summary

Once Relay ships manager-slot override support (ModifAmorphic/darktide-mod-relay#22), Curator can host AML (Auto Mod Loading and Ordering, Nexus mod 246) as a known mod and signal Relay per launch. Curator knows DMF; it may also know AML.

Scope

1. AML identity, mirroring the DMF pattern: Nexus mod 246, installed shape is a base/ folder (mod_manager.lua + an empty base.mod; the empty .mod is a Vortex-install marker, verified). Verify nothing special-cases the folder name base, and decide base-name collision behavior when another container's base folder is also named base.
2. mods.lst handling: exclude the AML container from mods.lst. Its base.mod is an empty marker, not a loadable mod; under the built-in manager it would just produce a failed entry, and under AML the list is ignored entirely.
3. Launch signal: when the active profile has AML enabled, append --mod-manager (path per Relay's anchor decision) to the launch arguments; derive per launch from profile state at the existing BuildLauncherArgs seam. AML disabled = not staged, no flag, built-in manager + mods.lst order as today.
4. While AML is enabled it owns ordering; Curator keeps writing mods.lst (the working fallback the moment AML is disabled, so persisted order stays meaningful). Treatment of the ordering UI (reorder/locks/policy are inert) is an open suggestion; no informational mechanism exists today.

Decisions to be made during implementation

• Ordering-UI treatment while AML is enabled.
• Flag path value form (depends on Relay's anchor decision).

[ModifAmorphic]

PR #231 implements this for the 1.1.0 milestone; the issue closes when the PR merges.