feat: add GlobalCaption to db/api for text annotation

[surygeng]

Description

Adds GlobalCaption as a new annotation shape type in the DB/API layer. S3 ingestion support was added in #603. This PR is a follow up to enable DB import and GraphQL API access.

Changes

• apiv2/schema/schema.yaml: Added GlobalCaption to annotation_file_shape_type_enum and updated shape_type pattern regex
• Codegen (make update-schema): Regenerated enums, DB models, GraphQL types, and Alembic migration
• test_infra/test_files/.../foo-1.0.json: Added GlobalCaption file entry to shared test fixture
• apiv2/db_import/tests/: Updated test expectations for the new annotation file

[surygeng]

@uermel Just to confirm, we should use "json" not "saber" here for the format, right?

[uermel]

@surygeng It should be the other way around. We decided to use "saber" instead of "json".

[uermel]

@surygeng I'm a bit surprised this passes tests without any changes to cryoet-data-portalbackend/apiv2/db_import/importers/annotation.py

Since we're using a glob for any json file here this presents the risk of matching both the annotation file and annotation metadata file (like I encountered when trying to test). How is that avoided here?

[manasaV3]

I think this file change is not needed. It is an empty change. :)

[surygeng]

Removed

[PALLAVIKHEDLE]

Thanks!

[surygeng]

@surygeng I'm a bit surprised this passes tests without any changes to cryoet-data-portalbackend/apiv2/db_import/importers/annotation.py

Since we're using a glob for any json file here this presents the risk of matching both the annotation file and annotation metadata file (like I encountered when trying to test). How is that avoided here?

I updated the glob pattern for the get_finder_args () function to exclude the _globalcaption.json files. The same logic for the s3 ingestion. Let's see if this works.

[surygeng]

@manasaV3 @uermel I added this _globalcaption.json test file here but not sure if it's necessary.