Use Chonky file browser with S3 data provided via GraphQL in the S3ObjectPicker component

[mbklein]

Summary

Replace client-side S3 object picker with Chonky file browser

Specific Changes in this PR

• Change GraphQL ListIngestBucketObjects to provide a folder-based listing using S3 ListObjectsV2 API
• Add S3ObjectProvider React component to interact with the GraphQL backend
• Refactor S3ObjectPicker React component to use Chonky file browser with data from S3ObjectProvider

Version bump required by the PR

See Semantic Versioning 2.0.0 for help discerning which is required.

• Patch
• Minor
• Major

Steps to Test

• Check both the Add a fileset and Replace fileset features of the Preservation tab
• Make sure the available files match the work type and fileset role
• Make sure the selected file is submitted and processes through the pipeline correctly

🚀 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

[kdid]

Looks great! 👍

[mathewjordan]

Works great for me!

[mathewjordan]

👍