DataStore autogenerated fields are not automatically populated during `amplify mock api`

How did you install the Amplify CLI?

pnpm

If applicable, what version of Node.js are you using?

Amplify CLI Version

10.5.1

What operating system are you using?

mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

n/a

Describe the bug

When mocking a GraphQL API that has Conflict Detection enabled, the fields used with DataStore such as _lastChangedAt are not automatically populated when creating records. Instead we are presented with an error:

{
  "data": {
    "createTodo": null
  },
  "errors": [
    {
      "message": "Cannot return null for non-nullable field Todo._lastChangedAt.",
      "locations": [
        {
          "line": 4,
          "column": 5
        }
      ],
      "path": [
        "createTodo",
        "_lastChangedAt"
      ]
    }
  ]
}

Expected behavior

Fields are automatically created with their expected values in mock

Reproduction steps

amplify init -y
amplify add api > GraphQL > Enable conflict detection
amplify mock api
attempt to perform createTodo mutation with all fields in the selection set
observe error

mutation CREATE_TODO {
  createTodo(input: {name: "hello todo"}) {
    _deleted
    _lastChangedAt
    _version
    createdAt
    description
    id
    name
    updatedAt
  }
}

Project Identifier

No response

Log output

``` # Put your logs below this line ```

Additional information