Add additional ProblemDetails default types and titles

[joegoldman2]

• You've read the Contributor Guide and Code of Conduct.
• You've included unit or integration tests for your change, where applicable.
• You've included inline docs for your change, where applicable.
• There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.

Description

This PR adds additional problem details titles and types for HTTP statuses 407, 410, 411, 413, 414, 416, 417, 421, 501, and 505.

[adityamandaleeka]

Thanks @joegoldman2. This seems fine to me... @martincostello @captainsafia, do we have any policy for which statuses we include here?

[martincostello]

Not that I'm aware of - I guess as long as it's an official code in the RFC it should be fine?

[captainsafia]

Yep, the Problem Details spec is very permissive about what status codes can be referenced in the payload (ref). The only thing it cautions about is that you make sure the status code in the Problem Details payload matches what is actually returned in the HTTP response (accounting for any proxies and whatnot).

With that in mind, we might want to consider if we want to go ahead and support all the status codes or just the finite set added here. @joegoldman2 Was there a particular reason you chose this subset to add?

[joegoldman2]

@joegoldman2 Was there a particular reason you chose this subset to add?

I needed to use a few (not all I added to this PR) and realized that default values were missing. I decided to add all missing standard (from the RFC) statuses.

[captainsafia]

LGTM! I double checked and this does cover all the status codes currently under Client Error and Server Error in the RFC.