Throw for invalid TryParse and BindAsync methods

[BrennanConroy]

If your TryParse method has a nullable out parameter and is a struct it fails to find the TryParse method and will throw:
System.InvalidOperationException : No public static bool MyBindAsyncRecord.TryParse(string, out MyBindAsyncRecord) method found for myBindAsyncRecord.

private record struct MyBindAsyncRecord(Uri Uri)
{
    public static bool TryParse(string? value, out MyBindAsyncRecord? result) =>
        throw new NotImplementedException();
}

This is because the method parameter type is Nullable`1[[MyBindAsyncRecord]]& and we pass MyBindAsyncRecord&

aspnetcore/src/Shared/ParameterBindingMethodCache.cs

Line 107 in de27715

methodInfo = type.GetMethod("TryParse", BindingFlags.Public | BindingFlags.Static, new[] { typeof(string), typeof(IFormatProvider), type.MakeByRefType() });

[halter73]

I'm not sure we should support this because it creates weird edge cases. For example, what should we do if a route handler takes in a non-nullable MyBindAsyncRecord and TryParse returns true but produces a null result?

I guess we could log an error similar to when TryParse return false, but what's wrong with just having the TryParse implementer return a default result?

[BrennanConroy]

Triage: We should instead throw for any TryParse methods that aren't conforming, and we would check for null struct as well.
And we should do this for BindAsync as well.