Limit shard failures accumulated by searches #99220
Description
Today we create an array of size getNumShards() to collect shard failures received during a search (on the first failure):
At high shard counts this array itself could be pretty large, and if a substantial number of shards fail then its contents will become massive. I'm pretty sure we don't need to accumulate all the failures in this situation, they're almost certainly not useful for the end-user or even for debugging. Could we instead just just track the first few failures and keep a count of the rest?
Relates #77466