Verbessert Deploys

Deploys check the database, the settings and the signing keys

A deploy refuses migrations the running release could notice, fails when the database cannot be reached, checks the site's settings, keeps releases a running job uses, and never signs links with a key made from the database password.

Internal. A live deploy now refuses, like a drop, a migration that renames or narrows a column, adds a NOT NULL column with no DEFAULT to a table in use, or drops a unique index or primary key; a person applies it by hand. The schema check fails when the database cannot be reached (every script in bin/ now exits 1 then) and lists what database/schema.sql has that the database lacks, failing on it once VERIFY_SCHEMA_FILE is 1. A new settings check reports APP_ENV missing from shared/.env and fills in empty signing keys with the key their links were signed with, so links already sent keep working; the live site no longer signs anything with a key made from the database password. Company Records' files are kept in the shared folder on dev sites too, the logs link follows SHARED_LOGS_DIR, a release a running script uses is not deleted, migration runs wait for one another before reading what is applied, and scheduled jobs send error alerts on the live site.