Invalidate filtering info on participants at the end of renameCollection

Upon finishing a rename, there is currently no filtering metadata refresh (e.g like we do in createCollectionCoordinator). This can lead to a situation where, after renaming a sharded collection, the 'toNss' filtering metadata is incorrectly left as 'unsharded'.