Warn about too new PHP version, don't block access completely

[LM-vb]

Tip

Help move this idea forward

• Use the 👍 reaction to show support for this feature.
• Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
• Subscribe to receive notifications about status changes and new comments.

---

Is your feature request related to a problem? Please describe.
Some Linux distributions moved from PHP 8.4 to 8.5. versioncheck.php blocks access to NC32 completely, stating that it is incompatible with PHP 8.5. However, it is not. By editing versioncheck.php and only one single 3rd party file (pimple -> Container.php) NC32 runs fine (at least for the apps we use).

Describe the solution you'd like
A notification similar to PostgreSQL in Administration -> Overview. If using a too new PostgreSQL NC works, but simply prints out a warning. It would save a hassle if this was done for PHP, too. Something like the following on the Overview page:
PHP version
PHP version "8.5" detected. PHP >=8.1 and <=8.4 is suggested for best performance, stability and functionality with this version of Nextcloud.

Additional context
I am aware that running NC outside of the recommended configuration is a risk (which has to be borne by the administrator). However, I have used newer PHP or PostgreSQL versions repeatedly in the last years and there were never any ill side effects.

[provokateurin]

We're not going to do this, almost every new PHP version has some minor changes that require fixes in Nextcloud. Only by allowing a specific range of versions we can ensure Nextcloud works correctly. Since we always support more than one minor version, you should pin the PHP you use using your distribution's package manager.

[LM-vb]

That's what I referred to in the section "Additional content". I am fully aware that there might be problems (yet as I stated, they are normally of minor impact and fairly easy to correct.) and that NC is not to blame for it (though I am also aware that people might...).

Regarding pinning the package version: that's no long term option. PHP depends on other libraries, other packages depend on this library, and so on and so forth. Pinning PHP (or any package), in my experience, does not really work and creates lots of headaches.