Dropping a database from the command line

Deletes a whole database through a shell tool rather than through SQL — dropdb, MongoDB's dropDatabase(), and the AWS RDS delete calls. It is the companion to block-destructive-sql, which sees the SQL statement but not dropdb myapp, because that command contains no DROP DATABASE phrase. Known over-match: dropdb --help is matched too, since the rule reads command text and cannot tell a help flag from a target. It does NOT cover a drop issued by application code or by a migration tool (see dd.migration-reset). A global flag between aws and rds is tolerated (aws --profile <p> rds delete-db-instance …, --region <r>); dropdb and dropDatabase() are single commands with no subcommand gap to exploit, and an absolute tool path still matches. A quoted MENTION is not a use: a search, a git commit -m message, an echo or a curl --data body that only names this command is left alone. That holds only while every shell metacharacter stays inside the quotes, so git commit -m "x" && … is still caught; and the carrier must be the first word, so sudo grep … is not exempt.