CloudSolrClient should not throw "Collection not found" with an out-dated ClusterState

Today, CloudSolrClient will locally fail if it's asked to send a request to a collection that it thinks does not exist due to its local ClusterState view being out-of-date.  We shouldn't fail!  And most SolrCloud tests should then remove their waitForState calls that follow collection creation!  Other stale state matters are out-of-scope.

Proposal: CloudSolrClient shouldn't try and be too smart.  Always route a request to Solr (any node); don't presume its state is up-to-date.  Maybe, after a response is received, it can check if its state has been updated and if not then explicitly get a new state.  Or not if that's too complicated.