ci: use php 8.5

[aaa2000]

Q	A
Branch	main
License	MIT

This PR updates the GitHub Actions workflow to use the latest stable PHP version, 8.5, in the CI pipeline.

[aaa2000]

The error of the "PHPUnit + Behat (PHP 8.5) (MongoDB)" job is already present on the main branch.

The errors of others behat jobs appear to be related to the following deprecation https://wiki.php.net/rfc/warnings-php-8-5#coercing_nan_to_other_types

<response>
	<title>An error occurred</title>
	<detail>Warning: unexpected NAN value was coerced to string in
		/code/vendor/doctrine/dbal/src/Driver/PDO/Statement.php line 26
	</detail>
	<status>500</status>
	<type>/errors/500</type>
	<trace>
		<function>handleError</function>
		<class>Behat\Testwork\Call\Handler\RuntimeCallHandler</class>
		<type><![CDATA[->]]></type>
	</trace>
	<trace>
		<file>/code/vendor/doctrine/dbal/src/Driver/PDO/Statement.php</file>
		<line>26</line>
		<function>bindValue</function>
		<class>PDOStatement</class>
		<type><![CDATA[->]]></type>
	</trace>

When the value is NaN, INF, or -INF, PDO::bindValue with PDO::PARAM_STR appears to convert to a string and throw the warning Warning: unexpected NAN value was coerced to string

Note: These values ​​are not compatible with SQLite, the value is 0, unlike postgres.

<?xml version="1.0"?><response><id>2</id><myFloatField>NAN</myFloatField></response>

<?xml version="1.0"?><response><id>3</id><myFloatField>INF</myFloatField></response>

`<?xml version="1.0"?>\n<response><id>4</id><myFloatField>-INF</myFloatField></response>

no idea how to fix it... Should the test be ignored in PHP 8.5?

[soyuka]

php-cs-fixer doesn't support 8.5 yet can you lower to 8.4 maybe?

[soyuka]

This failure is probably related to the changes:

--- Failed steps:

001 Example: | NaN   |                            # features/xml/deserialization.feature:74
      Then the response status code should be 201 # features/xml/deserialization.feature:68
        Current response status code is 500, but 201 expected. (Behat\Mink\Exception\ExpectationException)

839 scenarios (837 passed, 1 failed, 1 undefined)
5481 steps (5470 passed, 1 failed, 1 undefined, 9 skipped)
6m38.62s (324.02Mb)

Add a Then print last JSON response in there to know what's wrong. There are instructions in CONTRIBUTING.md if you need the commands to run the tests.