test(inference_async): drop tuple-rejection assertion from async embed validation

## Purpose

Tuples are actually valid embed inputs — the SDK's normalize_embed_inputs()
accepts them. The assertion that tuples should raise PineconeTypeError was
incorrect and caused the async integration test to fail against the real
backend (CI run 25460969544, job 74702736671) with a 400 INVALID_ARGUMENT
response instead of the expected client-side error.

## Solution

Deleted the three-line tuple block from test_embed_inputs_validation_rest_async
in tests/integration/test_inference_async.py. Mirrors the fix applied to the
sync sibling in CI-0054.

Author: jhamon

tests/integration/test_inference_async.py

@@ -432,10 +432,6 @@ async def test_embed_inputs_validation_rest_async(async_client: AsyncPinecone) -
     with pytest.raises(PineconeTypeError):
         await async_client.inference.embed(model=model, inputs=42)  # type: ignore[arg-type]
 
-    # unified-inf-0017: tuple rejected (not str or list)
-    with pytest.raises(PineconeTypeError):
-        await async_client.inference.embed(model=model, inputs=("a", "b"))  # type: ignore[arg-type]
-
     # unified-inf-0017: mixed list (string + integer) rejected
     with pytest.raises(PineconeTypeError):
         await async_client.inference.embed(model=model, inputs=["valid", 999])  # type: ignore[list-item]