feat: add config header and tests.

[Keeper-of-the-Keys]

• Resolves: [Bug]: Upgrade process re-renders config.php in a less readable/useable fashion #55171 (implements part of the suggested fix)
• Second attempt after feat: add config header #58886

Summary

config.php is re-rendered by nextcloud regularly removing comments and rendering constants into their values, nextcloud supports using multiple config files and renders their content into the main config.php without modifying the external files.
This PR adds a header to config.php warning the admin/user of this and suggesting the use of the multiple config files mechanism.

TODO

• In the future adding a footer that lists the files that were rendered into config.php in the order that they were included will probably help admins troubleshoot if a config variable is doubled up by mistake.
• Expand documentation more at https://docs.nextcloud.com/server/33/admin_manual/configuration_server/config_sample_php_parameters.html#multiple-merged-configuration-files with examples
• Add example/suggestion to use separate file for DB configuration https://docs.nextcloud.com/server/33/admin_manual/configuration_database/linux_database_configuration.html#ssl-for-mysql-database

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[Keeper-of-the-Keys]

Tagging: @provokateurin @miaulalala

[come-nc]

Please use a constant in the test instead of copy/pasting the comment multiple times.

Ideally, you can even have the comment in a public const in Config and use it in the test, so that if we change it later the test does not need to be changed.

[Keeper-of-the-Keys]

@come-nc thanks for the feedback!
I am so far only familiar with the few small areas of the NC code I touched, is there a preferred location/file that consts should be defined at?

[Keeper-of-the-Keys]

Or should it just be part of the Class?

[come-nc]

A public const in Config class is enough I think

[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.)