Improve handling of InterruptedException across codebase

[rohanKanojia]

We can clearly see in Sonar Bug report that there are lots of places in code where we're not handling InterruptedException properly. We're simply doing multi-catch and ignoring InterruptedException . For example, take a look at this code block:

kubernetes-client/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/base/BaseOperation.java

Lines 160 to 174 in e8c47dc

	private L listRequestHelper(URL url) {
	try {
	HttpUrl.Builder requestUrlBuilder = HttpUrl.get(url).newBuilder();
	addQueryStringParam(requestUrlBuilder, "labelSelector", getLabelQueryParam());
	addQueryStringParam(requestUrlBuilder, "fieldSelector", getFieldQueryParam());
	Request.Builder requestBuilder = new Request.Builder().get().url(requestUrlBuilder.build());
	L answer = handleResponse(requestBuilder, listType);
	updateApiVersion(answer);
	return answer;
	} catch (InterruptedException | ExecutionException | IOException e) {
	throw KubernetesClientException.launderThrowable(forOperationType("list"), e);
	}
	}

Usually, when a thread is interrupted, whoever is interrupting the thread, wants the thread to exit what it's currently doing. I think we should refactor all these places like this:

try{
    //some code
} catch (InterruptedException ie) {
    Thread.currentThread().interrupt();
    throw KubernetesClientException.launderThrowable(forOperationType("list"), e);
} catch (ExecutionException | IOException e) {
    throw KubernetesClientException.launderThrowable(forOperationType("list"), e);
}

[Shivkumar13]

/assign

[rohanKanojia]

I think there are some more occurrences apart from BaseOperation:

https://github.com/fabric8io/kubernetes-client/blob/master/openshift-client/src/main/java/io/fabric8/openshift/client/dsl/internal/ProjectRequestsOperationImpl.java

https://github.com/fabric8io/kubernetes-client/blob/master/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/internal/NamespaceVisitFromServerGetWatchDeleteRecreateWaitApplicableListImpl.java#L110

They can also be addressed in separate PR