Browser-wasm AOT: polymorphic recursion over struct type arguments

Same tiny console app, built twice per framework. ON: a generic method recurses into itself with its struct type arguments wrapped one level deeper (the shape of ILGPU's ArgumentMapper). OFF: the same walk with a non-generic field path. Times come from MSBuild's task performance summary of the publish binlog (MonoAOTCompiler = every mono-aot-cross pass, including the single-threaded aot-instances.dll dedup pass) and mono's own "Compiled" lines. Measured by this repo's GitHub Actions run(s): 44433620707.

FrameworkArmPublish wall timeMonoAOTCompiler task (all AOT passes) aot-instances compiledaot-instances emit JIT (Windows mono only)App
net9.0OFF (non-generic path)82.0 s5.2 s7,252n/arun
net9.0ON (polymorphic recursion)6,544 s (109.1 min)6,497 s (108.3 min)7,462n/arun
net10.0OFF (non-generic path)54.0 s5.2 s8,921n/arun
net10.0ON (polymorphic recursion)6,452 s (107.5 min)6,400 s (106.7 min)9,131n/arun
net11.0OFF (non-generic path)64.0 s6.2 s8,833n/arun
net11.0ON (polymorphic recursion)4,841 s (80.7 min)4,797 s (80.0 min)9,043n/arun

The aot-instances pass runs a collect phase before its emit phase (it re-compiles every input assembly to find shareable instances); mono prints no timing for that phase, but it is inside the MonoAOTCompiler task time. Each app prints its mapping result in the page; both arms must print ops 3 / 3 and exit 0.