`--no-verify` option doesn't exist

When a scan is run and a file matching a pattern is found, the output includes the [following statement](https://github.com/awslabs/git-secrets/blob/c11c229a8eebb3545e5fd3bab4e8aa55a7f19383/git-secrets#L160):

Use --no-verify if this is a one-time false positive

However, the `--no-verify` option doesn't exist, but it sounds like a nice feature.
Consider adding it or updating the output statement?

Start with the git-secrets script at the linked location around line 160 and inspect how the scan reports a matching pattern. Determine whether the intended resolution is to support --no-verify or correct the message, then verify that the resulting command-line behavior and output match the chosen resolution.

Written by the indexing model from the issue text.