Create ramenOpsNamespace such that it is not cleaned up when ramen operator is uninstalled

[raghavendra-talur]

In #1366 we added the functionality to automatically create the ramenOpsNamespace on the hub and the managed clusters. However, it is done using manifestwork for the managedclusters thereby removing the ramenops namespace when the operator is uninstalled.

Ideally, we want to keep the ramenOpsNamespace intact even after the operator is uninstalled.

[raghavendra-talur]

Looks like setting a deleteOption of orphan is possible with the latest OCM manifest work api but it is not available in the version of stolostron fork we use. Refer to https://github.com/open-cluster-management-io/api/blob/main/work/v1/types.go#L43 and https://open-cluster-management.io/concepts/manifestwork/#delete-options

[ShyamsundarR]

Looks like setting a deleteOption of orphan is possible with the latest OCM manifest work api but it is not available in the version of stolostron fork we use. Refer to https://github.com/open-cluster-management-io/api/blob/main/work/v1/types.go#L43 and https://open-cluster-management.io/concepts/manifestwork/#delete-options

This is being fixed here: 0f2df3e