Avoiding ParameterBindingMethodCache exceptions in MVC

[brunolins16]

In MVC, we don't need to throw an InvalidOperationException when an invalid TryParse is detected, since it will fallback to a Converter if one exists or to the previous behavior treating the type as a complex type. Also, the exception is already swallowed.

This PR includes a small change to the Microsoft.AspNetCore.Http.ParameterBindingMethodCache to avoid throwing and handling the exception in MVC.

The change consists of adding a new optional parameter to the constructor:

-public ParameterBindingMethodCache()
+public ParameterBindingMethodCache(bool throwOnInvalidMethod = true)

-public ParameterBindingMethodCache(bool preferNonGenericEnumParseOverload)
+public ParameterBindingMethodCache(bool preferNonGenericEnumParseOverload, bool throwOnInvalidMethod = true)

And the usage of this new information to avoid the exception to be thrown, eg:

if (candidateInterfaceMethodInfo is not null)
{  
-      throw new InvalidOperationException($"{TypeNameHelper.GetTypeDisplayName(type, fullName: false)} implements multiple interfaces defining a static {interfaceMethod} method causing ambiguity.");
+      return !throwOnInvalidMethod ? null : 
+                 throw new InvalidOperationException($"{TypeNameHelper.GetTypeDisplayName(type, fullName: false)} implements multiple interfaces defining a static {interfaceMethod} method causing ambiguity.");
}

Related PR: #40233

[pranavkm]

🚢 🇮🇹

[pranavkm]

You could consider moving line 651 above this and use UnderlyingOrModelType instead.