handle token request cases for authorization_code and refresh_token differently

[ylebre]

This PR is meant to fix #204

Work so far:

• split up the handling for authorization_code and refresh_token, so that we don't have 500 error anymore. This requires an update on the php-solid-auth code as well to get the refresh token information.

The current result is that the 500 error is solved, but replaced with a 401 instead. This one is coming from deeper in the token handling.

[ylebre]

The refresh token that is generated is actually an encoded json object, containing something like this:

{"client_id":"005c86034d936550c670c31da13fabcd","refresh_token_id":"09e9024478f33a713b707f198cacea66640df347a43f34ea1e42a30314c643f6b5cb31a91421bf43","access_token_id":"7556a6f81ab4e0d2fee33904804954459abf8ee6dc1aa20888adb6fdd0e92e8389a10d69c7aea166","scopes":["openid"],"user_id":"https:\\/\\/nextcloud.local\\/apps\\/solid\\/~alice\\/profile\\/card#me","expire_time":1753279371},

[ylebre]

Ok - it turned out the configuration passed to the oauth server was missing the client ID because it was in the POST instead of in the GET. After changing that around, it looks to be working now.

[Potherca]

I've added the PHP Codesniffer config as discussed in the comments.