fix(cron): Respect config_is_read_only config in in cron and console commands

[helmo]

• Resolves: https://help.nextcloud.com/t/running-cron-with-read-only-config/177221

Summary

I’d like to keep the config and application code read-only for the webserver as an extra security measure.
We have the config_is_read_only config boolean for that, but still occ and cron complain about not being the config file owner.

Even if they do have write access, which I think atleast cron should be able to do without.

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)

[helmo]

This has a merge conflict since #27613 was merged ... and I think that solved the same issue.

One minor detail remains, I've posted the string change in #44094