We should rely on the ws-manager last reported volume snapshot
information rather than use the volume snapshot client to find
the VolumeSnapshot object within the Kubernetes cluster.
This behavior is more close to how the ws-manager reports the last
volume snapshot information to server via ws-manager-bridge.
Signed-off-by: JenTing Hsiao <hsiaoairplane@gmail.com>