fix: don't implicitly parse URL encoded form data as JSON

[provinzkraut]

We currently parse URL encoded form data as JSON. This is arguably not the correct behaviour and can lead to serious bugs if something looks like JSON but isn't meant to be. It is also unexpected and there's no way for a user to control this.

This PR fixes the behaviour and adjusts the tests accordingly.

As an aside, it allows us to make fast-query-parsers optional as a speedup, which has now been moved to the standard and full extra.

[cofin]

LGTM and another welcomed change

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

100.0% Coverage
0.0% Duplication

[github-actions]

Documentation preview will be available shortly at https://litestar-org.github.io/litestar-docs-preview/2394

[MaxenceBouvier]

Hi,
I just wanted to make sure: does this change implies that the TODO list tutorial is somehow not up to date?
This tutorial indicates that the dict elements would be returned with a nice json exploration frontend interface, but what I have is plain text:

I am using:
Python version 3.12.2
Litestar version 2.6.1

Thanks.

[provinzkraut]

No, this has nothing to do with that. How the JSON presented in the browser is entirely up to your browser. The change only affects how incoming form data is parsed, not how data is rendered as JSON. As you can see, it is still JSON; Your browser just displays it differently than the one you're seeing a screenshot of in the tutorial.

The "nice json exploration frontend interface" is just how Firefox displays JSON.

[MaxenceBouvier]

@provinzkraut Thanks for your fast and detailed answer.
That actually helps a lot!
I would not have looked on the browser side for this json interface (non)issue.