fix cache quest lock condition

[self-transition]

In the previous PR #34, we added a synchronization lock to globalStore.get() to ensure that only one valid http(s) and wbsocket(s) request is sent for the same resource concurrently, but the lock is not sufficiently restrictive: the lock is only added if the request parameters are identical, for the following reason:

• The parameters passed to the dataprovider by the caller will only be used inside the dataprovider and not sent to the k8s api server, the actual request parameters sent to the api server should be determined by the dataprovider.
• In one globalstore instance, we should strictly ensure that only one list watch exists for a resource at a time, otherwise there will be unintended consequences.

This PR also adds the cancelquery logic that was missing: when the websocket readyState is CONNECTING, the connection should also be closed.

[huangjunjia]

LGTM

[tanbowensg]

LGTM