fix(admin): Revise opcache revalidation tuning section

[joshtrichards]

☑️ Resolves

• Try to make PHP revalidation values, suggestions, and trade-offs more apparent (main focus of this PR)
• Add big warnings about impact of lengthening frequency of revalidations and/or disabling outright
• Try to make the opcache tuning section a bit more organized (move things around more logically, add sub-headings)

Also, related to pending enhancement: nextcloud/server#45498

Note: The main thing that is perhaps controversial here is the PHP default of 2 versus 60 (not so much because we ever formally recommended changing it to 60, but because 60 is already being used in both the AIO and micro-services/community Docker image). I'm of the camp that PHP's default of 2 should be emphasized. And any deviation from that is fine, but the operator making that change is on their own (and expected to restart/etc if needed). Fortunately with the Docker images (at least ours), at least for Server itself, it's less of an issue since the code upgrades only happen through a container restart (but still a factor for config.php + potentially for app updates).

Historical (most relevant):

• Set recommend opcache.revalidate_freq docker#1718
• Use the recommended opcache settings docker#93
• OPcache recommendation wrong (opcache.enable_cli=1) #1439
• adjust opcache settings all-in-one#192
• update opcache settings all-in-one#199

🖼️ Screenshots

[joshtrichards]

/backport to stable29

[joshtrichards]

/backport to stable28

[joshtrichards]

/backport to stable27

[MichaIng]

Any server or app upgrade done from within the web interface triggers an OPcache reset. Only upgrades done via occ require a manual cache reset or PHP restart, if revalidation is disabled.

[MichaIng]

Suggested change

	Any Server/app upgrades or changes to ``config.php`` will then require restarting PHP (or otherwise manually clearing the cache or invalidating this particular script).
	Any Server/app upgrades via ``occ`` command or changes to ``config.php`` will then require restarting PHP (or otherwise manually clearing the cache or invalidating this particular script).

[kesselb]

Thanks 👍

I thought about removing validate_timestamp because it appears that many people do not understand the implications.

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)