This is the same issue as SERVER-104913, but for a different suite, so we should apply a similar testing strategy. 

• Increasing the size of the machine
• Running fewer tests concurrently

In SERVER-104913 we also create one smaller, generic search index for all tests that require it. It would be ideal if we could do something similar for hybrid search indexes.

It doesn't seem as straightforward to refactor the hybrid search tests to use shared indexes. We could start by using less dimensions for the indexes in the tests. In any case, I'm splitting these search test modifications into a separate ticket (SERVER-109343) to consider doing, if this BF shows up again after the Evergreen adjustments.