Issue with Reserved Field Names in Strapi 5 (After Upgrading from Version 4)
### Node Version

18.20.2

### NPM/Yarn/PNPM Version

PNPM 10.6.2

### Strapi Version

5.11.2

### Operating System

Windows 11

### Database

SQLite

### Javascript or Typescript

Javascript

### Reproduction URL

_No response_

### Bug Description

In Strapi 5, reserved field names have been introduced, which causes conflicts with existing collections where a `meta` field is used for components. When upgrading from version 4 to 5, the `meta` field remains in the collections, and when trying to add a new field via the admin panel, an error is displayed stating that the field `meta` is reserved.


### Steps to Reproduce

1. Upgrade Strapi from version 4 to version 5, with collections (branches, etc.) that include a `meta` field.
2. Open the admin panel and try to add a new field to the collection **branches**.
3. Receive an error message stating that the `meta` field is reserved.
4. Perform a migration using Knex and update the `schema.json`.
5. Although the `meta` field remains after starting the application, adding a new field causes data loss in the `branches_cmps` table.

### Expected Behavior

- After migration, if the field is renamed (e.g., to `metaData`), the data should be preserved, and the admin panel should correctly handle the addition of new fields.
- The system should ensure compatibility with reserved field names without data loss.

## Actual Behavior
- The admin panel prevents adding a new field because `meta` is reserved.
- Migrating via Knex (renaming the field) results in data loss from the `branches_cmps` table when a new field is added.

### Code Snippets

## Knex Migration Example
```javascript
exports.up = async function(knex) {
  await knex('branches_cmps')
    .where('field', 'meta')
    .update({ field: 'metaData' });
};

exports.down = async function(knex) {
  await knex('branches_cmps')
    .where('field', 'metaData')
    .update({ field: 'meta' });
};```

### Confirmation Checklist

- [x] I have checked the existing [issues](https://github.com/strapi/strapi/issues) for duplicates.
- [x] I agree to follow this project's [Code of Conduct](https://github.com/strapi/strapi/blob/develop/CODE_OF_CONDUCT.md).