Operator E2E Test to cover the FeatureStore customer resource with remote registry. #4823

This is an extended issue to 4792

We have to add the operator E2E test to cover following scenario.

• Deploy the feature store custom resource in one of of the kubernetes namespace.
• Deploy the another feature store custom resource in another namespace but should point to the registry using remote setting which should refer to the registry service created in the previous step.
• Assert all the conditions mentioned in the ticket-4792