Publishing deployment fails if trying to replace an exploded with a war deployment

[adietish]

steps:

1. ASSERT: have a wildfly server with an existing deployable folder that's not visible in vscode (ex.
   1. added the exploded deployable "kitchensink" (& published it)
   2. removed the server
   3. created the server again)
2. EXEC: pick "Add deployment to server" in ctx menu
3. EXEC: when asked pick "File" deployment and point it to kitchensink.war

Result: Publishing fails, I'm not told why. We maybe should add a "Clean" action in the ctx menu to allow us to remove the existing deployment.

[adietish]

@robstryker thoughts?

[robstryker]

I kinda expected this issue. This was a big issue back in jbt for a long time. I'll look into it.