okteto destroy command removes manifest information from config map even if the destroy command fails

[ifbyol]

Describe the bug

okteto destroy command removes manifest information from config map even if the destroy command fails. This provokes that the destroy all action in the backend doesn't work properly when a retry is done as the manifest is needed to know the commands to be executed on destroy

To Reproduce
Steps to reproduce the behavior:

1. Define an okteto manifest with a destroy section with a command you know it's going to fail (for example, https://github.com/ifbyol/test-okteto/blob/manifest-with-destroy-fail/okteto.yaml)
2. Deploy it via UI or using okteto deploy
3. Go to the UI and go to the YAML tab, you should see the manifest
4. Destroy the dev environment
5. Refresh the UI and you can see that the yaml is not empty (you can also check the configmap to verify that the manifest is not there)

Expected behavior
The manifest shouldn't be deleted from the config map until the configmap is completely desleted as part of the destroy operation. If the destroy fails, the configmap should keep the manifest information

Desktop (please complete the following information):

• 2.10.x

Additional context

You can see the manifest in the UI when the dev environment is deployed. You can see that there are a couple of commands in the destroy section and one of them executes a non-existent command

In the following screenshot you can see how the manifest is gone after executing a destroy

If you retry the destroy operation, it won't execute the destroy commands again

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days

[github-actions]

This issue is stale because it has been open for 60 days with no activity. Comment on this issue or it will be closed in 7 days