Refactor out use of camelCase for external IIIF in figures.yaml

[geealbers]

Before proceeding, make sure there isn’t an existing issue for this bug.

• I have searched the existing issues and determined this is a new bug.

Expected Behavior

Users should find a clear and regular naming patterns and structures for IIIF-related data attributes:

- id: "irises"    
  iiif_manifest: https://media.getty.edu/iiif/manifest/53be857e-41e8-4198-b45d-2e0f52d3051b/
  iiif_canvas: https://media.getty.edu/iiif/manifest/canvas/e5d29650-11f8-4897-9540-54a9dd65b04f.json
  src: figures/irises.jpg 

Or

- id: "irises"
  iiif_image: https://media.getty.edu/iiif/image/8c255d80-7382-46db-9fa8-892c0d37247e/

Actual Behavior

Instead, in the case of external IIIF images, users must use camel case manifestId, canvasId, and printImage

- id: "irises"    
  manifestId: https://media.getty.edu/iiif/manifest/53be857e-41e8-4198-b45d-2e0f52d3051b
  canvasId: https://media.getty.edu/iiif/manifest/canvas/e5d29650-11f8-4897-9540-54a9dd65b04f.json
  printImage: figures/irises.jpg
  src: figures/irises.jpg 

Steps to Reproduce

n/a

Version Numbers

[test-latest-41]
 quire-cli 1.0.0-rc.33
 quire-11ty 1.0.0-rc.41
 starter https://github.com/thegetty/quire-starter-default@2.10.0
[System]
 quire-cli 1.0.0-rc.33
 node v22.10.0
 npm 10.9.0
 os Darwin 22.6.0

Web Browser

No response

Relevant Terminal/Shell Output

Supporting Information

This issue was originally opened in Jira by @geealbers on 22/Aug/23 as DEV-13307.