…109.3 (#2367)

[main] Update dependencies from dotnet/arcade

…1112.1 (#2368)

[main] Update dependencies from dotnet/runtime

* Problem description and existing patterns
* Proposed solutions and some discussion of these

Co-authored-by: Eric Erhardt <[email protected]>

Currently this causes a crash in the linker due to null location scope.

Enabled by `--custom-data DisableMarkingOfCopyAssemblies=true` on the command line. Assumes that ALL assemblies on the input are in "copy" action (it doesn't validate this fact).

It disables marking basically fully - linker will go over all assemblies, and process them in "copy" mode (copy the original file over) and will call all the custom steps and so on, but it will do no marking (or very little, depends on descriptors and such which this doesn't disable).

This is intentionally non-discoverable feature, to be used only by the mono AOT toolchain.

…es (#2354)

Backports the file-based testing to release/6.0.2xx

Merge release/6.0.2xx to main

…2372)

The problematic scenario is if there's a "copy" assembly with a forwarder to a "link" assembly with a forwarder. The forwarder is for a nested class.
Test for #2359.

Also improved the test infra to print out errors from ilasm if they happen.

This implementation doesn't skip members without attributes, so it found some
bugs as well.

The new Cecil fixes the deterministic MVID and PDB checksum.
Details in dotnet/cecil#31.

…elease/6.0.2xx-to-main

Merge release/6.0.2xx to main

When create a type reference for the target of a type forwarder, if the type forwarder is for a nested type, we have to build a whole tree of type references for all of the declaring types and not just the final nested type.

Enabled tests which were already added for this case (and fixed a bug in them)

These were causing dotnet format to produce warnings because
they didn't have code fixes available. There are still some IDE0060
rule violations left over that I am not fixing here because they occur
in test projects (and I didn't want to silence all such warnings in the
test projects).

Co-authored-by: vitek-karas <[email protected]>

…1126.4 (#2403)

[main] Update dependencies from dotnet/runtime

…126.4 (#2402)

[main] Update dependencies from dotnet/arcade