Lock bug

[GrantBirki]

Lock Bug

This pull request does the following:

• Resolves a bug where .lock <env> --reason <text> commands are treated like a .wcid or .lock --info command when they shouldn't be. This only occurs when .lock commands had a lockInfoFlag inside of the command. Something like .lock --reason "doing a branch-deploy" would be treated as a .lock -d command because of the -d in -deploy 😵‍💫 . This has been resolved by adding a leading space character to the lockInfoFlags
• Adds a lot more debug logging to the lock() methods

---

resolves: #186

[GrantBirki]

Now it works!