Follow-up: Very slow JSON:API responses when images are stored on AWS bucket

Copy of re-rolled patch from https://git.drupalcode.org/project/consumer_image_styles/-/merge_request... (#8) attached, to be used with composer, see "Patches from drupal.org merge request URLs are dangerous".

patch in #9 is working for me. Prior to applying this patch, the jsonapi route for files was failing and logging errors for property validation:

Errors: [
  {
    "property": "",
    "pointer": "",
    "message": "The property data is not defined and the definition does not allow additional properties",
    "constraint": "additionalProp",
    "context": 1
  },
  {
    "property": "data",
    "pointer": "\/data",
    "message": "Array value found, but a null is required",
    "constraint": "type",
    "context": 1
  },
  {
    "property": "data",
    "pointer": "\/data",
    "message": "Array value found, but an object is required",
    "constraint": "type",
    "context": 1
  },
  {
    "property": "data[1].links.placeholder.href",
    "pointer": "\/data\/1\/links\/placeholder\/href",
    "message": "Invalid URL format",
    "constraint": "format",
    "context": 1,
    "format": "uri-reference"
  },
  {
    "property": "data[1].links.placeholder",
    "pointer": "\/data\/1\/links\/placeholder",
    "message": "Object value found, but a string is required",
    "constraint": "type",
    "context": 1
  },
  {
    "property": "data[1].links.placeholder",
    "pointer": "\/data\/1\/links\/placeholder",
    "message": "Failed to match exactly one schema",
    "constraint": "oneOf",
    "context": 1
  },
  {
    "property": "data",
    "pointer": "\/data",
    "message": "Failed to match exactly one schema",
    "constraint": "oneOf",
    "context": 1
  },
  {
    "property": "errors",
    "pointer": "\/errors",
    "message": "The property errors is required",
    "constraint": "required",
    "context": 1
  },
  {
    "property": "",
    "pointer": "",
    "message": "Failed to match exactly one schema",
    "constraint": "oneOf",
    "context": 1
  }
]

Hi! patch #9 works for me, before patch we had problem with API exactly like @apmsooner. RTBC! TY!

also thanks @apmsooner for posting that error here, we found this patch thanks to it!

Patch #9 works for me as well. We were also experiencing schema validation errors as described in #10