PDF file sets should not have a pyramid location

[kdid]

Summary

On the preservation report, Auxiliary files of type PDF were erroring because the pyramid was not found.

Specific Changes in this PR

• Update Meadow.Data.FileSets.pyramid_uri_for() so that it does not return a pyramid location for a file set with mime-type of application/pdf

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 preservation report for a pdf Auxiliary file.
• The pyramid_location column should be empty and the pyramid_exists column value should be N/A

🚀 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

[mbklein]

Approving this as the least invasive way to make this work, but I wonder if instead of excluding specific types from having pyramids, we should only include it for the specific types that need them? (e.g., image/* and anything with a zoomable thumbnail?)

[kdid]

@mbklein - good catch. I made an adjustment. Thanks.