Fix: Move required from array schema to object schema inside items

[gregmillz]

In the openapi spec, the required array belongs on the object schema inside items, not on the parent array schema (see data types)

• Fix required field placement in array item schemas. It was being set on the array schema itself instead of inside items, but it should have been in the object schema. The fix for this is in the function generateSchemaForResponseValue.

Example:
Incorrect: required object properties are in the array schema

lineItems:
  type: array
  required:  # `required` is not a valid keyword on type: array
    - productId
    - quantity
  items:
    type: object
    properties:
      productId:
        type: string
      quantity:
        type: integer
      note:
        type: string

Correct: required object properties are in the object schema:

lineItems:
  type: array
  items:
    type: object
    required:
      - productId
      - quantity
    properties:
      productId:
        type: string
      quantity:
        type: integer
      note:
        type: string

• Add missing required field support for responses that are arrays of objects. For example, when Laravel APIs return a collection, it's wrapped in a data key like { "data": [{"name": "foo"}]} but you can call JsonResource::withoutWrapping() to get an array instead: [{"name": "foo"}]. The fix for this is in generateResponseContentSpec.

[gregmillz]

I see this is the same issue as this PR, but I would like to see if the test changes are fixed with this pr

[gregmillz]

CI is fixed by separate this other PR: https://github.com/knuckleswtf/scribe/pull/1071/changes

[gregmillz]

Hi @shalvah! Is there a release schedule? No rush. The package is great, so would like to help improve it with this change :)