Query/Form: Use serde_path_to_error to report fields that failed to parse

[Turbo87]

Motivation

I've started using the Query extractor more and more over the past couple of days and noticed that its error messages don't help the user in understanding which field specifically failed to parse.

Solution

This solves the problem roughly similar to our existing usage of serde_path_to_error in the Json extractor. The resulting error messages change from e.g.

Failed to deserialize query string: invalid digit found in string

to

Failed to deserialize query string: my_broken_field: invalid digit found in string

[Turbo87]

/cc @jplatte :)

[jplatte]

Mind doing the same thing for Form and both serde_html_form extractors in axum-extra?

Also, changelog entries

[Turbo87]

doing the same thing for Form

it looks like the Form extractor already includes the field name (from the tests: Invalid URL: Cannot parse reswith value123123-123-123123: UUID parsing failed: invalid group count: expected 5, found 3), though in this case the user isn't aware of the internal name of the field, so I don't know how useful that even is 😅

and both serde_html_form extractors in axum-extra?

yeah, I'll add it to the other Query extractor too

[Turbo87]

nevermind, I was looking at the Path extractor, not the Form extractor... 🤦‍♂️

too early in the morning 😂

[Turbo87]

Mind doing the same thing for Form and both serde_html_form extractors in axum-extra?

Also, changelog entries

alright, should all be done now :)

[jplatte]

Thanks!