Fix ordering of Gemini inlined batch responses

[neo-con]

Summary

Fixes #1909.

The Gemini API can return inlinedResponses out of request order for batch jobs that use inlined_requests. This change preserves the original request order by stamping an SDK-reserved order marker on each inlined request and reordering returned inlined responses by that marker when the full marker set is present and valid.

This change keeps the behavior conservative:

• if any response is missing the reserved order marker, preserve backend order
• if any response has a non-numeric order marker, preserve backend order
• caller-provided metadata cannot override the reserved SDK order marker

Changes

• add a reserved internal metadata key for inlined request ordering
• stamp deterministic request-order metadata onto Gemini inlined batch requests
• reorder Gemini inlined batch responses by that metadata before returning them
• strip the internal order marker from returned response metadata after reordering
• add regression coverage for:
  • internal order metadata injection
  • reserved-key override behavior
  • deterministic response reordering
  • missing-metadata fallback
  • non-numeric fallback

Testing

env -u GOOGLE_API_KEY -u GEMINI_API_KEY python -m py_compile google/genai/batches.py google/genai/tests/conftest.py google/genai/tests/batches/test_create_with_inlined_requests.py

env -u GOOGLE_API_KEY -u GEMINI_API_KEY GOOGLE_GENAI_REPLAYS_DIRECTORY=/tmp/google-genai-replays pytest google/genai/tests/batches/test_create_with_inlined_requests.py --mode replay -q

env -u GOOGLE_API_KEY -u GEMINI_API_KEY GOOGLE_GENAI_REPLAYS_DIRECTORY=/tmp/google-genai-replays pytest google/genai/tests/batches/test_create_with_inlined_requests.py -k internal_order_metadata --mode replay -q

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Venkaiahbabuneelam]

Hi @neo-con, Thanks for reaching out us!

Looks like the branch is out of date, Can you please update the branch.
Thanks

[neo-con]

updated branch, thnx

[hoangducnhatminh]

Hi @neo-con is this branch merged?

btw, thank you for your support

[github-actions]

This pull request has been marked as stale because it has been inactive for 14 days with no activity. It will be closed in 2 days if no further activity occurs.

[github-actions]

This pull request was closed because it has been inactive for 16 days. Please reopen or submit a new PR if you need further assistance. Thanks!