Allow NamespaceSync to create flows in non-existent namespaces

[trevordavidlawrence]

Feature description

Feature

NamespaceSync with sourceOfTruth: GIT fails when the target namespace does exist yet. This appears to be intentional behavior, since there's a specific message shown in this scenario:

The namespace does not exist in the 'main' tenant

The feature is this: either allow this task to handle this case like SyncFlows does or else add an optional boolean property controlling this behavior.

Use-case

I'm using NamespaceSync to "bootstrap" a fresh environment, and I will on occasion be promoting new namespaces of flows through environments using this strategy. I'd like to use NamespaceSync for all of these needs since it matches my deployment philosophy so well, but this check is causing some friction. It's not a hard thing to work around, though.

Notes

I'm willing to contribute a PR, I just wanted to be certain whether this was an explicitly intended behavior for a reason I'm not aware of.