Update change management to increase the criticality of SQL scripts (via cron or manually) from C4 to C2.

Current Situation

Presently our change management process allows a broad definition of things which can be run against the production database.

Any procedural invocation such as a SQL script, a ruby script module, a rake task which is performed on a production console server, either using gitlab-rails or gitlab-rake.

This allows for any changes to be flagged as C4 which should perhaps be given deeper scrutiny via the approval steps of higher criticalities.

Desired Outcome

It is clear to users of the change management process what criticalities to use for all database-related changes.

Acceptance Criteria

• MR is submitted and merged updating the base criticality for database changes to C2 for all database change cases which do not meet C1.