Allow liquibase checksums to be cleared (automatically on a daily basis) and lock table to be emptied via console.

Sometime systems give a 504 when trying to access the console.

According to cloudwatch it is trying to acquire a liquibase lock during startup but it is already taken.

This causes the startup to loop because the system will not get past this and it will cause AWS to startup a new instance with the same problem.

It is not clear when this occurs to prevent this loop from happening (if possible) allow liquibase checksums to be cleared automatically on a daily basis and lock table to be emptied via the console.

**Reporter**
Vivienne Jacobs

**Screenshots**
If applicable, add screenshots to help explain your problem.