Avoid clearing filtering metadata after failed metadata refresh

This clearFilteringMetadata after a failed refresh shouldn't be necessary. In that situation, the exception is already propagated to the caller of onShardVersionMismatch. Moreover, on the following requests that do shardVersion checking, onShardVersion mismatch should already be called anyway if the metadata was unknown/stale; so there should not be a need to explicitly clear the filtering metadata.