JWT: The XML input and output aren't supported

[adriendupuis]

🎫 Issue	IBX-10444

Related PRs:

• IBX-8356: Reworked Ibexa\Core\MVC\Symfony\Security\Authentication\AuthenticatorInterface usages to comply with Symfony-based authentication #101
• Update JWT documentation-developer#3108

Description:

• XML isn't supported by JWT since IBX-8356: Reworked Ibexa\Core\MVC\Symfony\Security\Authentication\AuthenticatorInterface usages to comply with Symfony-based authentication #101
• IBX-10444: Content-Type and Acceptheaders mustn't be documented as header parameters, they're automatically documented from requestBody.content and responses.<status>.content keys

For QA:

On an instance, look at REST API doc at /api/ibexa/v2/doc#/User%20Token/api_usertokenjwt_post, and eventually click the "Try it out" button.

Before the fix:

• There are mandatory Accept and Content-Type parameter fields that are ignored.
• You can choose between XML and JSON requests and responses.
• If you test with an XML input, you get an error.
• If you test with a XML reponse, you get a JSON response anyway.

After the fix:

Documentation:

REST API Reference should be automatically fixed on next commerce-skeleton release tagging.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[tomaszszopinski]

QA approved on Ibexa DXP 5.0.