delete command is missing support for force deletion parameter resulting in error

[shouah]

The 'delete-job' and 'delete-job-schedule' and 'delete-call' and 'delete-call-schedule' commands are all missing support for the optional '--force' or '-f' option causing execution error due to incompatible syntax and resulting in unexpected duplicated setup since the delete command with the optional option is not taking effect:

USAGE:
delete-job JOB_NAME [--force]
delete-job-schedule JOB_NAME SCHEDULE_GUID [--force]
delete-call CALL_NAME [--force]
delete-call-schedule CALL_NAME SCHEDULE_GUID [--force]

OPTIONS:
--force, -f Force deletion without confirmation

[norman-abramovitz]

We are currently deciding if we are going to implement the prompt if the force is not set or just treat the force flag as a noop argument since the command's default behavior is to delete.

[norman-abramovitz]

It was decided not to add the prompt at this time to avoid making behavioral changes, so we can do a small point release for this enhancement.

[norman-abramovitz]

PR #2 Will be fixing this issue. Also added a --prompt flag that actually performs the prompting. This does not change the current behavior since an explicit action is required to get the confirmation to function. The --prompt flag will not be externally documented through the plugin at this time. Once the PR gets through the pipeline, this issue will be closed.