`.lock` and `.unlock` commands not working with `--reason`

[GrantBirki]

Pretty much the title. Opening this issue to track fixes

initially detected here: #185 (comment)

---

Debug log:

Trigger ".deploy" not found in the comment body
Trigger ".noop" not found in the comment body
Trigger ".unlock" not found in the comment body
Trigger ".help" not found in the comment body
Trigger ".wcid" not found in the comment body
##[debug]'--reason' found in comment body: .lock --reason "i am testing out the brancheploy action" - attempting to remove for environment checks
##[debug]comment body after '--reason' removal: .lock 
##[debug]Using default environment for lock request
##[debug]reason: "i am testing out the branch-deploy action"
##[debug]detected lock env: production
##[debug]detected lock global: false
##[debug]constructed lock branch: production-branch-deploy-lock
##[debug]lock branch production-branch-deploy-lock does not exist
no active deployment locks found
##[debug]Node Action run completed with exit code 0

[GrantBirki]

Getting called with ##[debug]lock() called with detailsOnly: true when it should not be 🤔

[GrantBirki]

🤦 it was matching -d in the branch-deploy text on my sample comment... Guess these need spaces to be a bit safer