fix colocated site deployment logic on failed namespace creation

[JPadovano1483]

Issue:
During the initial deployment of a colocated site, if the creation of the namespace fails, you get logs indicating this, and then immediately get a log saying the namespace was created, even if it was not. The controller then enters a failing reconciliation loop where it keeps trying to apply resources to a non-existent namespace.

Steps to reproduce:
The easiest way I found to force this condition is to:

1. create a backbone with a colocated namespace
2. after it is deployed, delete it from the GUI
3. immediately, while the namespace is still in the terminating state, recreate the backbone with the same name (or at least the same colocated namespace)
4. View the MC logs, looking for logs related to the creation of the colocated namespace and the errors related to the attempted creation of resources in that non-existent namespace.

See the following comment for more context and where the issue is stemming from:
#127 (comment)