AOT: annotate Spectre.Console.AnsiConsole.WriteException usage in AssertCommand

[jeremydmiller]

Surfaced by IsAotCompatible=true on Weasel.Core (landed in Weasel 9.0 foundation):

warning IL3050: Using member 'Spectre.Console.AnsiConsole.WriteException(Exception, ExceptionFormats)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. ExceptionFormatter is currently not supported for AOT.

Location: src/Weasel.Core/CommandLine/AssertCommand.cs:34

This is in a CLI command — dev-time tool, not production hot path. Per the JasperFx 2.0 cold-start/AOT pillar pattern, the fix is to annotate the consuming method (or class) with [RequiresDynamicCode] so the warning propagates to AOT-publishing consumers as a precise diagnostic rather than getting silently swallowed.

Tracked under pillar JasperFx/jasperfx#213.

[jeremydmiller]

Resolved by PR #272 (merged into 9.0).

Annotates AssertCommand.Execute with [RequiresDynamicCode] so the IL3050 diagnostic from AnsiConsole.WriteException propagates to AOT-publishing consumers as a precise warning at the entry point. Per the issue's guidance, this is the minimum-blast-radius fix — db-assert is a dev-time CLI tool, not a hot path.