update ingestion-helper status and version endpoints to support lists of multiple imports

[dwnoble]

This enables the DCP ingestion workflow to update multiple imports at once

Submit with: datacommonsorg/datacommons#134

• API Payload Schema Change: Updated UpdateImportStatusRequest and UpdateImportVersionRequest models to accept lists of imports under an imports parameter instead of single-import fields.
• Service Endpoint Processing: Refactored the /imports/status and /imports/version route handlers to iterate and update GCS file version/provenance logs and Spanner status records for multiple imports in a single call.
• Workflow & Helper Updates: Adjusted caller definitions in import-automation-workflow.yaml and import_helper.py to match the new list-based HTTP request structures.
• Test Coverage: Added new unit test scenarios in app_test.py mock-validating the updated endpoints with lists of multiple imports.
• Documentation: Updated the API overview table in the ingestion-helper README.md to document the list support.

[codacy-production]

Not up to standards ⛔

🔴 Issues 1 minor

Alerts:
⚠ 1 issue (≤ 0 issues of at least minor severity)

Results:
1 new issue

Category	Results
CodeStyle	1 minor

View in Codacy

🟢 Metrics 5 complexity

Metric	Results
Complexity	5

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[gemini-code-assist]

Code Review

This pull request updates the import automation workflow and ingestion helper to support batch processing of multiple imports. The API endpoints and schemas for updating import status and version have been modified to accept lists of imports, and corresponding unit tests and documentation have been updated. The review feedback suggests two key improvements: replacing the 'Z' suffix in next_refresh with '+00:00' to maintain compatibility with Python versions prior to 3.11, and extracting the caller identity retrieval outside of the loop in update_import_version to avoid redundant JWT decoding and verification.

[vish-cs]

Currently, it has a single status for all the imports. Would it make sense to make status as part of the import item so each import can have its own status?

[vish-cs]

We also need to update https://github.com/datacommonsorg/data/blob/master/import-automation/executor/scripts/update_import_version.sh as per this change

[vish-cs]

Currently, it has a single status for all the imports. Would it make sense to make status as part of the import item so each import can have its own status?

I am approving the PR to unblock DCP work but it might be helpful to update this.

[gmechali]

Thanks Dan!

[dwnoble]

Currently, it has a single status for all the imports. Would it make sense to make status as part of the import item so each import can have its own status?

Updated!