previously, we had assert.soon() call listSearchIndexes repeatedly until the specified index is queryable. assert.soon() times out after 10 minutes on evergreen (And after 1.5 minutes otherwise). I'm finding that the full 10 minutes is really needed for vector search indexes, which take quite a bit of time to finish building
3:59

and now that we are moving the logic for search index replication from javascript to c++, we want to similarly set the maxtimeout in search_index_command_testing_helper to be dynamic depending on if we're running on evergreen or locally.

to do this we should introduce a new server parameter that resmoke passes to mongos/mongod. then search_index_command_testing_helper can check the value of that server parameter