feat: add subcommands to allow app locking and unlocking

Unlocking an app will not stop running deploys, so users may need to clean up. However, it is useful for deploys that fail in unusual ways that cause the lock to stay around.

Closes #2883

tests/unit/10_apps.bats

@@ -150,4 +150,35 @@ teardown () {
   echo "status: "$status
   assert_success
 
+}
+
+@test "(apps) apps:lock/unlock" {
+  create_app
+
+  run bash -c "dokku apps:report $TEST_APP --locked"
+  echo "output: "$output
+  echo "status: "$status
+  assert_output "false"
+
+  run bash -c "dokku apps:lock $TEST_APP"
+  echo "output: "$output
+  echo "status: "$status
+  assert_success
+
+  run bash -c "dokku apps:report $TEST_APP --locked"
+  echo "output: "$output
+  echo "status: "$status
+  assert_output "true"
+
+  run bash -c "dokku apps:unlock $TEST_APP"
+  echo "output: "$output
+  echo "status: "$status
+  assert_success
+
+  run bash -c "dokku apps:report $TEST_APP --locked"
+  echo "output: "$output
+  echo "status: "$status
+  assert_output "false"
+
+  destroy_app
 }