Fix: CritterStackDefaults.GeneratedCodeOutputPath does not change output dir

[carcer]

Closes #2080

Problem

When users configure:

builder.Services.CritterStackDefaults(profile =>
{
    profile.GeneratedCodeOutputPath = "Test/ABC";
});

Wolverine ignores this setting because:

1. WolverineOptions.ReadJasperFxOptions() doesn't copy GeneratedCodeOutputPath from JasperFxOptions (unlike Marten which does)
2. The DEBUG path adjustment in HostBuilderExtensions overwrites any configured path

Changes

• WolverineOptions.cs - Added GeneratedCodeOutputPath propagation from JasperFxOptions in ReadJasperFxOptions(), following Marten's pattern
• HostBuilderExtensions.cs - Restructured DEBUG path adjustment to respect user-configured paths and AutoResolveProjectRoot setting
• docs/guide/codegen.md - Added documentation section "Customizing the Generated Code Output Path"
• CodegenUsage.cs - Added code snippets for documentation

Tests

• Added 5 new tests in generated_code_output_path_configuration.cs verifying the fix

Test Plan

• All existing tests pass
• New unit tests verify GeneratedCodeOutputPath propagation
• New integration test verifies CritterStackDefaults flows to Wolverine
• Verified explicit Wolverine configuration takes precedence