Maintenance mode agent

Code has merge conflicts that need to be resolved.

updated with commits from 1.0.x

Tests have multiple fails, so knocking back to needs work: the branch is out of dateso it may be as simple as updating the fork to fix.

I'm not sure I personally can see a use case for this agent, since the ability to take a site offline isn't something I can see most people wanting to defer to an AI. Might this be better as a separate module, or at least with some documentation in the new docs folder to detail when you would see it being used?

wouters_f → closed merge request !10

wouters_f → changed the visibility of the branch 3487199-maintenance-mode-agent to hidden.

Pipeline is now green.

I just wanted to see how hard it was to add one.
if you don't want it in, also good.
I do feel that we should expose as much admin actions as possible however, otherwise the bot will feel like a less capable version of the admin interface and it will feel not as powerfull. Just my thoughts.