chore: complete google-cloud-firestore migration to librarian

[jskeet]

No description provided.

[jskeet]

@parthea I've split this PR into multiple commits to make it clearer - it looks like all the changes come from either reformatting or regenerating with legacylibrarian. The deleted lines are worrying though - I'm not sure whether those are breaking changes or not.

[gemini-code-assist]

Code Review

This pull request transitions the google-cloud-firestore library to automated generation, updates the supported Python versions to 3.9 and above, and introduces an expiration_offset field to the TTL configuration. The update also removes several Pipeline and Vector Search exports from the public API, which appears to be a regression that could break existing user code. Additionally, there is an inconsistency between the TtlConfig docstring, which states that sub-second precision is rejected, and a unit test that includes nanoseconds in the offset.

I am having trouble creating individual review comments. Click here to see my feedback.

packages/google-cloud-firestore/google/cloud/firestore/init.py (33-34)

The removal of AsyncPipeline and AsyncPipelineStream (along with other Pipeline-related exports like Pipeline, FindNearestOptions, and Ordering later in this file) appears to be a regression. These features were recently added to the Firestore SDK, and their removal from the public API will break existing user code. Please verify if these components should be preserved during the librarian migration.

packages/google-cloud-firestore/google/cloud/firestore_admin_v1/types/field.py (148-150)

The docstring states that "Values more precise than seconds are rejected" for expiration_offset. However, the corresponding unit test in test_firestore_admin.py (line 20834) includes a nanos value ("nanos": 543). This inconsistency should be resolved: if the API indeed rejects sub-second precision, the test data should be updated to reflect this restriction; otherwise, the docstring should be corrected.

[jskeet]

It looks like a lot of the changes in __init__.py were introduced in #16549 - I wonder whether this is a matter of modifying firestore-integration.yaml to reflect those changes? cc @daniel-sanche

[chalmerlowe]

LGTM, pending a fix for the failing system test.

[jskeet]

@parthea: I've now added two commits to this PR:

• Changing the integration replacements file
• Regenerating again with librarian

Now the __init__.py files are unaffected.