Data Model deploy failure

### 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

d2tkk8ivw3yqtf

### Region

ap-southeast-2

### Environment name

dev

### Figma File Version (if applicable)

_No response_

### Amplify CLI Version

10.6.2

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

_No response_

### What operating system are you using?

Mac

### Browser type?

Safari 16.3

### Describe the bug

Hi, I have a data model consisting of a set of 28 tables, 20 ENUM's and various relationships between the tables (40 are 1:1 and 15 are 1:many).

I am trying to add a new table and relationships via Amplify Studio, and the Data Model editor allows me to do this but when I click Save and Deploy, it says it has deployed the new data model but the new table is not there. When I inspect my Dynamo DB tables, the new table is also not present. When I look at Cloudformation there have been no new stacks run so it looks like the deploy was not submitted.

I have an ERD I can send privately, but would prefer not to share it publicly here.

### Expected behavior

When I add a new table or relationship, or update and existing table or relationship, it will be saved and deployed in Amplify Studio Data Modelling.

### Reproduction steps

1. Add new table (called 'RiskManagementProcessesDataSet') to existing Data Model
2. Update an existing relationship in the 'Disclosure' table to point to this new table (previous table was called 'Risk Management Processes'
3. Click 'Save and Deploy'

### Project Identifier

_No response_

### Additional information

I have repeated these steps and see exactly the same behaviour - no Cloudformation changes and no new tables in DynamoDB, but Amplify Studio shows it has updated successfully.

Start in Amplify Studio’s Data Model editor and trace the Save and Deploy flow for the named model changes; compare the reported success with CloudFormation stack activity and DynamoDB table state. Reproduce with RiskManagementProcessesDataSet and the Disclosure relationship, then verify that the new table and relationship appear in the deployed backend.

Written by the indexing model from the issue text.