Update default interfaces support

[marek-safar]

We need to refresh our default interface support to align with the latest runtime change mostly about diamond scenarios and constrained/boxed calls

Runtime

• Update tests to include the latest changes from CoreCLR
  • https://github.com/dotnet/coreclr/tree/master/tests/src/Regressions/coreclr
  • https://github.com/dotnet/coreclr/tree/master/tests/src/Loader/classloader/DefaultInterfaceMethods
• Fix Crash executing static methods on interfaces #13319 (static methods on interfaces)
• Fix Crash executing default implemented property in interface  #13374 (tests fixed, crash is still happening)
• Fix Unexpected System.NotSupportedException in presence of default interface implementations #13401
• Fix Unexpected System.MethodAccessException is thrown for a protected method declared in an interface #13467
• Fix Crash at runtime likely related to protected accessibility of a method declared in an interface. #13466
• Fix ilasm ILAsm: adds 'virtual' attribute to sealed default interface methods #13508
• Fix Unexpected System.MethodAccessException is thrown for a method call of a class that implements a protected interface inside another interface #13550
• Fix Unexpected System.MethodAccessException is thrown for a static protected method declared in an interface  #13551

BCL

• Add System.Reflection support for dim with tests (see Make it possible to Reflection.Emit default interface methods dotnet/coreclr#16257)
• Add System.Reflection.Emit support for dim (see Fix reflection to work with default interface methods dotnet/coreclr#16034)

[vargaz]

The only failing test is constrained2.il, not sure how that test is supposed to work.

[MichalStrehovsky]

The only failing test is constrained2.il, not sure how that test is supposed to work.

@vargaz Can you double check you ran all the tests? In light of #13401 I would expect this test to fail too because Mono is throwing the old exception for ambiguous dispatch (before the new exception got approved).

Cc @AlekseyTs