CleanupOnStop option does not clean up resources if DevWorkspace Deployment does not exist

[amisevsk]

Description

When enabling the config.workspace.cleanupOnStop option in the DevWorkspaceOperatorConfig, the setting is ignored when cleaning up workspaces that do not have a deployment. This means that services, configmaps, etc. are potentially left in the namespace for stopped workspaces.

How To Reproduce

1. Enable cleanupOnStop in the DevWorkspaceOperatorConfig
2. Create a workspace that fails before the deployment is created (e.g. by using an invalid routingClass -- cluster-tls on a Kubernetes cluster)
3. When workspace fails, DevWorkspaceRouting is left on cluster

Expected behavior

Cleanup should be processed the same regardless of whether or not Deployment exists.

Additional context