[bug] If create operation ends up unexpectedly it creates a lock and destroy is not working

[adrianriobo]

To solve this issue we can create a flag --force on the destroy operation to force remove the lock before running the destroy.

Hint: check how that would work on remote backed url

{"level":"error","msg":"failed to refresh stack: exit status 255\ncode: 255\nstdout: \nstderr: error: the stack is currently locked by 1 lock(s). Either wait for the other process(es) to end or delete the lock file with `pulumi cancel`.\n  file:///workspace/.pulumi/locks/organization/windows-desktop/stackCreateWindowsDesktop-windows-desktop/ce397a2f-81f2-416a-9311-dbb93c9b9e6a.json: created by root@a75f5d17663b (pid 46) at 2023-12-04T15:55:41Z\n\n","time":"2023-12-04T16:04:53Z"}

[adrianriobo]

on remote backed-url, the error message says use pulumi cancel s3://....