`sqlcmd delete` fails for a context that has a container, and the container has been manually deleted already

[stuartpa]

We could do a couple of things

1. Allow the delete to succeed, and log a warning
2. Fail the delete, and require a --force (but right now --force is bound to the scenario around not deleteing a context if user data is present in the contianer)

[JyotikaGargg]

In My point of view , we should go with #1 option (Allow the delete to succeed, and log a warning),
As the container has already been deleted for that context ,so there is no point of failing a delete in this case.
We should definitely be explicit in our message about the scenario