See #259383

make a 'this site is disabled' page target. people can override this by changing the provision_apache_disabled_url variable (no visible ui for that yet). See #259383

just removing the config file will not work since the default vhost kicks in and still allows the disabled site to work. instead, we
create a custom vhost configuration file that redirects to a "disabled" url (that we should make configurable eventually).

right now that url is just $base_url/disabled, which gives a page not found, but i'll work more on that

temporarily disable chown error flag on sites directory creation. the permissions are being correctly set, but the tests are failing

compare users properly in check_path. also apply the same logic on chgrp, which was missing. add information on why the check failed in the error message

add status code for 'not run', set to 1 since it's the default value in hosting. DB_ERROR is now '128'.

fix the name of the user/group variables: it's now provision_script_user and provision_web_group, to follow what is configured in hosting

now this works, but the hostmaster user (or the script running the cron job) needs to be part of the provision_web_group

Site creation is working again. There was a bug in the db switching code, and some permission changes that i commented out for now while i am testing

documentation nitpick: add -p to the mkdir call because vhosts.d is in the config/ subdir, which also needs to be created

this fixes a few warnings