Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

…/templating (#15454)

Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>

…15461)

Co-authored-by: Michael Simons <[email protected]>
Co-authored-by: Přemek Vysoký <[email protected]>

…ols project (#15447)

…ference-packages (#15459)

[main] Update dependencies from dotnet/arcade, dotnet/source-build-reference-packages

…15465)

…lt in CI (#15463)

This is on platforms where the Mono SDK is supported.

When Mono JIT compiles `Main()`, it encounters a call to `new ConsoleRunner()`. Unlike CoreCLR, Mono JIT **attempts to resolve all field types of ConsoleRunner at JIT compilation time**, rather than deferring resolution until runtime.
The problem arises because some fields inside `ConsoleRunner` depend on **assemblies that are only resolvable via the assembly resolve event handler**. However, this resolve handler is **only installed after Main() has been compiled and execution starts**. As a result, Mono JIT fails when it attempts to load these types too early, leading to runtime errors.

This is a workaround for a limitation in Mono JIT by moving the instantiation to an another function.

Allow `Main()` to execute first**, ensuring that the assembly resolve handler is installed **before** `ConsoleRunner` is instantiated 

See: dotnet/runtime#60550

Co-authored-by: Přemek Vysoký <[email protected]>

…sh (#15466)

#15472)