SERVER-104913 created a generic vector search index that was accessible between jstests running on the same resmoke job. Under the hood, the createGenericVectorSearchIndex() function would call $listSearchIndexes and only create the index if it wasn't already present. However, since the mongot_community_e2e_sharded_collections suite runs with 5 concurrent resmoke jobs, if tests that require a generic search index are split across jobs, each will have to individually create a vector search index, increasing patch build runtimes as well as the possibility of an OOM error as more tests are added in this suite in the future.

We should investigate adding a hook that runs at fixture start in the mongot_community_e2e_sharded_collections suite, so that tests running on different jobs can all access the same vector index. There's a POC of it here, but we should be able to safely remove the dropSearchIndex hook at fixture teardown because resmoke will automatically clean up the environment at the end of the suite.