Composite item models inherit lighting from the first entry in the `models` field

When using an item model definition with a composite model, lighting conditions are inherited from the first entry in the list of models.

For example, compositing a block model and an item model causes the item to be shaded like a block and viceversa, depending on what’s first on the list of models.

Diamond shaded like a block (Transformation field is irrelevant, it’s just so the diamond is properly visible).

assets/minecraft/items/diamond.json

{
  "model": {
    "type": "composite",
    "models": [
      {
        "type": "model",
        "model": "minecraft:block/pumpkin",
        "transformation": {
          "translation": [0, 0, 0],
          "left_rotation": [0, 0, 0, 1],
          "right_rotation": [0, 0, 0, 1],
          "scale": [1, 1, 1]
        }
      },
      {
        "type": "model",
        "model": "minecraft:item/diamond",
        "transformation": {
          "translation": [0, 0, 1],
          "left_rotation": [0, 0, 0, 1],
          "right_rotation": [0, 0, 0, 1],
          "scale": [1, 1, 1]
        }
      }
    ]
  }
}

The attachment is a resource pack that exclusively reproduces the issue, overriding the diamond item model definition.