This test expects an internal transaction using the router role on a shard to remote target a specific number of times, which requires the shard's router shard version cache to be up to date, otherwise a stale cache can trigger a retry. Ideally this test shouldn't require a specific number of attempts, but as a short term fix, update the test to pre-warm the cache to avoid retries. This is only a problem now that the router and shard caches were split by SERVER-95393.