Model binding infinite recursion or infinite loop with complex collections

[dougbu]

Describe the bug

Collections of complex types may bind unconditionally until int.MaxValue elements are reached. This relates to #4939 but involves built-in model binders.

Similarly, nested types may recursively bind until the stack is exhausted. This may relate to #6616.

To Reproduce

Steps to reproduce the behavior:

1. Using the current version of ASP.NET Core i.e. master
2. Create a simple model such as

   private class LocationInfo
   {
       [FromHeader]
       public string GpsCoordinates { get; set; }
   
       public int Zipcode { get; set; }
   }

3. Add an action to a controller or a handler to a page with a List<LocationInfo> argument
4. Post a request containing a `` header to the action
5. Experience extremely slow response (as the collection fills up int.MaxValue items

Expected behavior

Expect model binding to detect the problem and throw an Exception informing the developer.

Additional context

Beyond [FromHeader], the problem may occur with [FromServices] or a custom greedy model binder. It's possible other models can cause infinite recursion or extremely large collections in model binding.

[dougbu]

Hit this while working on #6793. That fix does not cover all the cases (obviously).

We need reasonable limits e.g. MvcOptions.MaxModelBindingCollectionSize and MvcOptions.MaxModelBindingRecursionDepth to put the breaks on these cases and inform the developer. Suggest the new options should default to match FormReader.DefaultValueCountLimit and MvcOptions.MaxValidationDepth, respectively.

[dougbu]

Self-assigning since I started working on this after hitting the problem while doing #6793.