Fix race condition in integration test cleanup

[jhamon]

Problem

I noticed that tests were failing for the python 3.13 build of tests/integration/data_grpc_futures tests after merging PR #510 to main.

Solution

Context:

• When tests are run on a PR branch, they only execute on python 3.9.
• When tests they run on main, tests run for both python 3.9 and 3.13.

What I observed:

• In this case, the python 3.13 build of newly added tests tests/integration/data_grpc_futures was consistently failing with "Unauthorized" errors
• Despite the confusing error message from the API, this "Unauthorized" response was being returned when making calls for an index that no longer exists.
• Why did the index no longer exist? Because the python 3.9 build of the same tests was completing first and nuking the index before the 3.13 python build completes.
• Why would the 3.9 tests delete an index being used by the 3.13 tests?
• A test helper was assigning a deterministic name for the index that was the same for both builds.

Solution:

• Revert back to a randomized name strategy for indexes. Need to rethink deterministic names later before we can use something like VCR to playback recorded API calls in testing.
• Reenable 3.13 tests on PR branches for now so we can see that this change takes care of the problem observed on merge

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Infrastructure change (CI configs, etc)

Test Plan

Should see all tests passing even when 3.9 and 3.13 tests are run together on PR push.

[rohanshah18]

LGTM!