Adds iiif_collection field to collection index

[kdid]

Summary

• Adds iiif_collection field to collection index so that it can be used by the API
• Note: this is part 1 of the work for issue 5174 - part 2 will take place in DCAPI

Specific Changes in this PR

• Adds iiif_collection field to collection index

Version bump required by the PR

See Semantic Versioning 2.0.0 for help discerning which is required.

• Patch
• Minor
• Major

Steps to Test

• Perform after Meadow reindex
• Look at a collection Opensearch response document (either in Kibana or the regular DCAPI response (not the as=iiif one))
• Confirm that you see a iiif_collection field
• Confirm that the field links to the correct as=iiif collection response in DCAPI

🚀 Deployment Notes

Note - if you check any of these boxes go to the (always open) main <- staging PR and add detailed notes and instructions to help out others who may end up deploying your changes to production

• Backward compatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
• Backwards-incompatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
• Requires data migration
• Requires database triggers disabled during deployment/migration
• Requires reindex
• Terraform changes
  • Adds/requires new or changed Terraform variables
• Pipeline configuration changes (requires mix meadow.pipeline.setup run)
• Requires new variable added to miscellany
• Specific deployment synchronization instructions with other apps/API's
• Other specific instructions/tasks

Tested/Verified

• End users/stakeholders