Incoming PHP-FPM changes for httpd ProxyPass and ProxyPassMatch handling.

Apology for opening this nextcloud possible non issue but wanted to double check with you some changes that I'm adding to php-fpm in terms of handling PATH_INFO from ProxyPass and ProxyPassMatch which is quite inconsistent. The issue with those is that they send URL encoded path info and script file name. I applied the PATH_INFO fix in https://github.com/php/php-src/issues/17643 which just got merged and should be part of 8.3.18. It will basically provide the PATH_INFO decode. This should be quite safe but wanted to check with you in case you do some special handling for that. Another one which would decode the whole script path will be probably just for master: https://github.com/php/php-src/issues/17645 . But if you can see any issue with that, I could maybe add some switch for it.

This is mainly created here because there were some issues reported here. This in relation to past bugs https://github.com/nextcloud/server/issues/37852 and https://github.com/nextcloud/server/issues/40943 create by @mrAceT .

Feel free to close this it if you don't see any potential issues for nextcloud after this gets implemented.

Start by reading php-src issues 17643 and 17645, then review the related Nextcloud issues 37852 and 40943. Trace how Nextcloud handles PATH_INFO from PHP-FPM behind Apache ProxyPass and ProxyPassMatch; no specific file or test is named, so completion would be a confirmed compatibility assessment and identification of any required Nextcloud change.