PR Summary

After switching to the latest dotnet 6 preview.7 SDK, we started to see the "Bad IL format" failure as shown below (see the reported dotnet bug here).
This is because a new preview feature is enabled in preview.7, which allows an interface to have abstract static methods (see the blog post). The type System.Int16 implements much more interfaces in preview.7, and many of them declare abstract static properties. However, the abstract static properties cannot be invoked with GetValue(null) reflection API, and doing so results in this Bad IL format error.

The recommendation from .NET team is to ignore static virtual/abstract members on an interface, especially as the set of APIs may change with .NET 7.

This PR includes the following changes:

1. Update .NET adapter to ignore static virtual methods/properties on interface
2. Given DisablePrivateReflectionAttribute is already obsolete and there is no restriction on private reflection in .NET Core, remove DisallowPrivateReflection and uses of it from our code.
3. The way how PopulateMethodReflectionTable handles interface was to call type.GetInterfaceMap(interfaceType) and use the interface methods from the returned mapping object. The static non-virtual methods on an interface will be missed in this way, so, this is changed to call interfaceType.GetMethods(bindingFlags) directly.
4. A minor change to the parameter type of the MethodCacheEntry constructor, to avoid unneeded array creation.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.