#93045500 vs 503 error handling is not consistent
Description
For 5xx status code we have two different cases right now * configuration errors, which need to respond with 500 * maintenance mode, which is a 503 response
In 10.4.10 always 500 is returned, in master and 10.4 branch currently 503. This should be streamlined.
Also the 500 or 503 site error handler in maintenace middleware isn’t invoked as the maintenace mode middleware is executed before the site resolver middleware.