one terraform force-unlock does not recognize LOCK_ID or -force argument

[wvxavier]

Issue Summary

Command one terraform force-unlock does not recognize LOCK_ID or -force argument

Steps to Reproduce the Problem

1. First authenticate to acquire any terraform state
2. Type one auth gsuite and assume an admin role one dnx-assume
3. Secondly initiate your stack of AWS resources example: one terraform init --workspace nonprod-ap-southeast-2-dev
4. You can find your LOCK_ID running a terraform plan: one terraform plan --workspace nonprod-ap-southeast-2-dev

5. Once you obtained the LOCK_ID run one terraform force-unlock 999cb9bae-999-9h9b-c9k9-99999l99k99

   The following error message will appear:

   
   Setting workspace to nonprod-ap-southeast-2-dev
   unlock requires a lock id argument
   Usage: terraform force-unlock LOCK_ID [DIR]
   
   Manually unlock the state for the defined configuration.
   
   This will not modify your infrastructure. This command removes the lock on the
   state for the current workspace. The behavior of this lock is dependent
   on the backend being used. Local state files cannot be unlocked by another
   process.

Options:

-force Don't ask for input for unlock confirmation.

 6. Trying with `--force` argument:

one terraform force-unlock -force 999cb9bae-999-9h9b-c9k9-99999l99k99 Usage: one terraform force-unlock [OPTIONS] LOCK_ID Try 'one terraform force-unlock --help' for help.

Error: no such option: -f

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

## Specifications

  - Version: Run `one --version`
  _Latest_
  `one, version 0.7.2`
  - Platform: (macOS / linux)
  `macOS Big Sur Version 11.3.1`
  - Installation method: (Binary / PyPI)
  `PyPI`