don't throw a misleading exception upon a BadHttpRequestException

[LilahTovMoon]

don't throw a misleading exception upon a BadHttpRequestException

Description

If a request is too large, you get a screen telling you, "A valid antiforgery token was not provided with the request. Add an antiforgery token, or disable antiforgery validation for this endpoint." This leads a developer to try and debug why the anti forgery token isn't working rather than telling them the issue is that the request is too large when there's nothing wrong with the anti forgery token. The issue is that the request body is too large.

Current behavior:

Desired behavior:

Fixes #40810

[dotnet-policy-service]

Thanks for your PR, @LilahTovMoon. Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[dotnet-policy-service]

Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime.
To make sure no conflicting changes have occurred, please rerun validation before merging. You can do this by leaving an /azp run comment here (requires commit rights), or by simply closing and reopening.