DefaultBinder named parameter support skipping default parameters

[buyaa-n]

DefaultBinder supports named parameters and parameters with defaults could be ignored, but only if the named parameters provided in order Example:

public static class Sample
{
    public static void SampleMethod(string param1, int param2 = 0, bool param3 = false) { }
}

public void Test( )
{
var methods = typeof(Sample).GetMethods();
var flags = BindingFlags.Public | BindingFlags.Static;

// Binding the named parameters in order works fine.
var methodArgs = new object[] { "value", 2 };
var paramNames = new string[] {"param1", "param2"}
var method = Type.DefaultBinder.BindToMethod(flags, methods, ref methodArgs, null, null, paramNames , out var _);

// Skipping an optional parameter `param2`  causes IndexOutOfRangeException exception
methodArgs = new object[] { "value", true };
paramNames = new string[] {"param1", "param3"}
var method = Type.DefaultBinder.BindToMethod(flags, methods, ref methodArgs, null, null, paramNames , out var _);

The PR fixes the above issue and also a case where all the unspecified parameters have default values and further makes sure the binding updates work with Type.InvokeMember(...)

Fixes #66237

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-reflection
See info in area-owners.md if you want to be subscribed.

Issue Details

---

DefaultBinder supports named parameters and parameters with defaults could be ignored, but only if the named parameters provided in order Example:

public static class Sample
{
    public static void SampleMethod(string param1, int param2 = 0, bool param3 = false) { }
}

public void Test( )
{
var methods = typeof(Sample).GetMethods();
var flags = BindingFlags.Public | BindingFlags.Static;

// Binding the named parameters in order works fine.
var methodArgs = new object[] { "value", 2 };
var paramNames = new string[] {"param1", "param2"}
var method = Type.DefaultBinder.BindToMethod(flags, methods, ref methodArgs, null, null, paramNames , out var _);

// Skipping an optional parameter `param2`  causes IndexOutOfRangeException exception
methodArgs = new object[] { "value", true };
paramNames = new string[] {"param1", "param3"}
var method = Type.DefaultBinder.BindToMethod(flags, methods, ref methodArgs, null, null, paramNames , out var _);

The PR fixes the above issue and also a case where all the unspecified parameters have default values and further makes sure the binding updates work with Type.InvokeMember(...)

Fixes #66237

Author:	buyaa-n
Assignees:	buyaa-n
Labels:	area-System.Reflection
Milestone:	-

[buyaa-n]

Test failures unrelated dotnet/winforms#8829 and reported #13757

[buyaa-n]

paramOrder[i][j] array keeps track of real(defined) position of parameters, in case args count is less than defined parameters its not tracked, in order to support any number of named parameters defined in any order we need to keep track of all parameters

[buyaa-n]

In case only 1st and 3rd named arguments provided from the 4 parameters the order in paramOrder[i] will be {0, 2, 1, 3} and argTypes[paramOrder[i][1]] will cause IndexOutOfBoundsException, therefore first need to check if current parameter is within provided arguments range

[buyaa-n]

Until this row nothing is changed except using index I defined above: int index = paramOrder[i][j]; instead of each paramOrder[i][j] access

[buyaa-n]

in case index not within the provided arguments range (index >= args.Length) allow it to continue only if the parameter has default value and BindingFlags.OptionalParamBinding is set

[buyaa-n]

Here the provided args count is less than defined parameters the missing arguments filled with defaults, but it was not supporting skipped arguments, the update fixes that

[buyaa-n]

This method reorders named arguments in parameter order, again it was not supporting if any of the arguments skipped

[buyaa-n]

Failure looks unrelated, filed an issue, merging