 Relation tables are not renamed/migrated if the component table is larger than IDENTIFIER_MAX_LENGTH


## Bug report

Relation tables are not renamed/migrated if the component table is larger than `IDENTIFIER_MAX_LENGTH` (55 characters).

Migration: 5.0.0-rename-identifiers-longer-than-max-length

### Required System information

- Node.js version: v20
- NPM version: 10.8.2
- Strapi version: 5.4.2
- Database: sqlite
- Operating system: linux


### Describe the bug

Hello, we are having an issue with the migration process (5.0.0-rename-identifiers-longer-than-max-length) of Strapi. From 4.25.10, we are migrating to 5.4.2 and there are unexpected behaviors with the migrations process for the relation table of a component. 

Several of our components have a table name table larger than IDENTIFIER_MAX_LENGTH. Hence, in the database, we can have this kind of table:
```
# main table
components_module_05_my_component_have_a_name_larger_than_identifier_max_length
# relation table
components_module_05_my_component_have_a_name_larger_than_identifier_max_length_example_links
```

When  we run the migration process, `components_module_05_my_component_have_a_name_larger_than_identifier_max_length` will be correctly renamed. For instance, with this name `components_module_05_my_component_have_a_name_8795adke`.

Unfortunately, `components_module_05_my_component_have_a_name_larger_than_identifier_max_length_example_links` will not be migrated/renamed. The migration will later fail because Strapi does a select request with the new name of this table (but the table still has its old name). 

We did some investigation and we saw something weird with this call `const diffs = findDiffs(md);`  (file: @strapi/database/dist/index.js.)
`diffs` contain the full name and the short name of the table. For our first table, we can find something like this:

```  
{
	full: {
  	index: 173,
  	key: 'tableName',
  	tableName: ‘components_module_05_my_component_have_a_name_larger_than_identifier_max_length’
	},
	short: {
  	index: 173,
  	key: 'tableName',
  	tableName: ‘components_module_05_my_component_have_a_name_8795adke’
	}
  },
```  
`components_module_05_my_component_have_a_name_larger_than_identifier_max_length` is correctly renamed to 
`‘components_module_05_my_component_have_a_name_8795adke’` in the database. 

But for the second table, we find something like this:
```  
 {
	full: {
  	index: 163,
  	key: 'tableName',
  	tableName: 'components_module_05_my_component_have_a_name_8795_adke_example_links'
	},
	short: {
  	index: 163,
  	key: 'tableName',
  	tableName: '‘components_module_05_my_component_have_a_name_8795adke_example_lnk'
	}
  }
```  
full.tableName is incorrect for this table. Hence, it seems logical that the table is not migrated correctly. The correct name of the table, `components_module_05_my_component_have_a_name_larger_than_identifier_max_length_example_links` can not be found in the diffs variable. 

We assume that the migration processes takes the new name of the parent table to migrate the relation table, and this create an issue if the parent table is also migrated. 

We hope that this indication can help you find the issue. We were not able to go further in the code and find the explicit line where the translation between the old and new name takes place. 


### Expected behavior

We should find something like this in the  `const diffs = findDiffs(md);`

```
 {
	full: {
  	index: 163,
  	key: 'tableName',
  	tableName: 'components_module_05_my_component_have_a_name_larger_than_identifier_max_length_example_links'
	},
	short: {
  	index: 163,
  	key: 'tableName',
  	tableName: '‘components_module_05_my_component_have_a_name_8795adke_example_lnk'
	}
  }


```
