field tags causes naming conflict and throws an save error

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d27ep6bgfd7ubg

### Region

us-east-1

### Environment name

dev

### Figma File Version (if applicable)

_No response_

### Amplify CLI Version

_No response_

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

_No response_

### What operating system are you using?

_No response_

### Browser type?

_No response_

### Describe the bug

consider the following model

```
type Product @model @auth(rules: [{allow: public}]) {
id: ID!
name: String
description: String
price: String
category: String
tags: [String]
Inventories: [Inventory] @hasMany(indexName: "byProduct", fields: ["id"])
cartID: ID @index(name: "byCart")
}
```

this causes the form to render but any changes to the form causes an error

```
The number of resources passed must be greater than 0 and less than 100.
```

refreshing the page causes the form to not open at all.

workaround:

renaming the field `tags` to anything else works as expected.

### Expected behavior

provide a better error message and load field that contains tags

### Reproduction steps

1. create a data model with a tags field and deploy
2. create a form with the model
3. make a new field on form
4. observe save error

### Project Identifier

_No response_

### Additional information

_No response_

Start by reproducing the issue with the Product model shown in the report, including its tags field, then create and edit a form as described. Trace the form load and save entry points involved in the failure; done means the tags field loads, form changes save successfully, and unsupported cases produce a clearer error.

Written by the indexing model from the issue text.