Optimize Kubernetes/OpenShift API access

[rhuss]

Description

The current way how the API client is created and how the decision is made whether an OpenShift or Kubernetes client should be used in burried mostly in ClusterAccess but also used differently e.g. in WatchMojo or Fabric8ServiceHub. It also looks like that during the detection phase some unnecessary API calls are performed.

Actually, this should be refactored:

• That's there is only a single spot where the client is created
• When the mode is specified, a cluster must not be called. This is especially important for offline mode, where the whole build slows down when this detection can't be performed

See #895 for a first start how the client could be created when the mode is known.

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

[stale]

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!