Quay operator attempts to create a route when route and tls components are unamanged

This is a bug affecting Quay operator-based installations.

The operator always attempts to create a temporary fake route to check if the cluster supports Route API.

This check not be done when the route and tls components are marked as unmanaged since these components are supposed to be managed manually by the user.

The issue is 100% reproducible

Steps:
**

1. Install Quay operator
2. Deploy QuayRegistry making sure that route and tls are marked as unmanaged
3. Observe that a route called xxxx-test-route will be created.

Code snippet: GitHub