v4CompatibilityMode graphql relations are not compatible, output differs

## Bug report

### Required System information

<!-- Please ensure you are using the Node LTS version (18, 20, or 22) -->
<!-- Strapi v3 is no longer supported, please update to Strapi v4 -->
<!-- If you are reporting a frontend bug please provide error logs after setting STRAPI_ENFORCE_SOURCEMAPS=true in your .env -->
<!-- This environment variable makes frontend errors easier to read and trace -->

- Node.js version: 20
- NPM version: yarn 1.22
- Strapi version: 5.3.0
- Database: sqlite
- Operating system: macos
- Is your project Javascript or Typescript: js

<!-- Did you know you can run `yarn strapi report` or `npm run strapi report` to get this information easier? -->

### Describe the bug

I'm running a graphql query with `v4CompatibilityMode` enabled, but the output is not the same as in v4. 
The relations return differently. 

my query:

```
query q($slug: String!) {
  vehicle: vehiclesVehicles(filters: {slug: {eq: $slug}}) {
    data {
      id
      attributes {
        accessories(pagination: {limit: 9999}) {
          data {
            id
            attributes {
              title
            }
          }
        }
      }
    }
  }
}

 ```

v4 output is `vehicle.data[].accessories.data[].id`:

```
"data": {
    "vehicle": {
      "data": [
        {
          "id": "2514",
          "attributes": {
            "accessories": {
              "data": [
                {
                  "id": "3820",
                  "attributes": {
                    "title": "Manhattangrijs"
                  }
                },
                {
                  "id": "3821",
                  "attributes": {
                    "title": "Velgen, lichtmetaal 7J x 17 \"5-dubbelspaak\"-design"
                  }
                },
                {
                  "id": "57",
                  "attributes": {
                    "title": "buitenspiegels elektrisch verstel- en verwarmbaar"
                  }
                },
```

v5 output is `vehicle.data[].accessories[].data.id`:

```
{
  "data": {
    "vehicle": [
      {
        "data": {
          "id": "2514",
          "attributes": {
            "accessories": [
              {
                "data": {
                  "id": "3820",
                  "attributes": {
                    "title": "Manhattangrijs"
                  }
                }
              },
              {
                "data": {
                  "id": "3821",
                  "attributes": {
                    "title": "Velgen, lichtmetaal 7J x 17 \"5-dubbelspaak\"-design"
                  }
                }
              },
              {
                "data": {
                  "id": "57",
                  "attributes": {
                    "title": "buitenspiegels elektrisch verstel- en verwarmbaar"
                  }
                }
              },
```

so on v4 the `accessories.data` is the array, on v5 `accessories` is the array with `data` blocks inside every entry.

### Steps to reproduce the behavior

both in v4 and v5:
1. Have a content-type with a relation
2. install graphql
3. fetch the relation in a graphql query

see how output is not the same.

### Expected behavior

Output to be the same, to be compatible
