Wrong relation table created with wrong engine,charset and collate make relations impossible to input (with solution proposal)
### Node Version

v20.18.0

### NPM/Yarn/PNPM Version

NPM 10.8.2

### Strapi Version

5.10.0

### Operating System

Linux (Debian/Ubuntu)

### Database

MariaDB

### Javascript or Typescript

Typescript

### Reproduction URL

_No response_

### Bug Description

I've created a relation between 'relances' (one personal table) and up_users. The purpose is to have many 'relances' for one user.

With the content manager, the input of a relation is impossible.  On the relances table, the visual feedback is green (as sucess), but the relation isn't stored at all. Using the up_users, the feedback is 'Internal server error' (and the relation is of course not stored).

In fact, (see later), the table of "lnk" is badly built, and mysql refuses any insertion.

### Steps to Reproduce

1. Created content with Strapi
2. Create a tables named 'relances'
3. Add a relation between 'relances' and 'up_users' (many relances for one user)
4. Input some relances and users
5. I'm not sure this is the cause, but first, i've created a relation with users (admin), when i saw i was wrong, i've changed the relation to be on 'permissions' users.
6. Try to input some relations. It won't work.

### Expected Behavior

Be able to input relation with the content manager (or with sql client).

### Logs

```shell

```

### Code Snippets

_No response_

### Media

_No response_

### Additional information

What is important, is that when i've dumped the base, i've got:

CREATE TABLE `up_users` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `document_id` varchar(255) DEFAULT NULL,
  `username` varchar(255) DEFAULT NULL,
  `email` varchar(255) DEFAULT NULL,
  `provider` varchar(255) DEFAULT NULL,
  `password` varchar(255) DEFAULT NULL,
  `reset_password_token` varchar(255) DEFAULT NULL,
  `confirmation_token` varchar(255) DEFAULT NULL,
  `confirmed` tinyint(1) DEFAULT NULL,
  `blocked` tinyint(1) DEFAULT NULL,
  `created_at` datetime(6) DEFAULT NULL,
  `updated_at` datetime(6) DEFAULT NULL,
  `published_at` datetime(6) DEFAULT NULL,
  `created_by_id` int(10) unsigned DEFAULT NULL,
  `updated_by_id` int(10) unsigned DEFAULT NULL,
  `locale` varchar(255) DEFAULT NULL,
  `user_mobile` varchar(255) DEFAULT NULL,
  `user_signature` longtext DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `up_users_documents_idx` (`document_id`,`locale`,`published_at`),
  KEY `up_users_created_by_id_fk` (`created_by_id`),
  KEY `up_users_updated_by_id_fk` (`updated_by_id`)
) **ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;**

CREATE TABLE `relances` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `document_id` varchar(255) DEFAULT NULL,
  `relance_nomdevis` varchar(255) DEFAULT NULL,
  `relance_datecreation` datetime(6) DEFAULT NULL,
  `relance_nbconsultations` int(11) DEFAULT NULL,
  `relance_datederniereconsultation` datetime(6) DEFAULT NULL,
  `relance_pour` varchar(255) DEFAULT NULL,
  `relance_societe` varchar(255) DEFAULT NULL,
  `relance_montant` double DEFAULT NULL,
  `relance_statut` varchar(255) DEFAULT NULL,
  `relance_statut_date` datetime(6) DEFAULT NULL,
  `created_at` datetime(6) DEFAULT NULL,
  `updated_at` datetime(6) DEFAULT NULL,
  `published_at` datetime(6) DEFAULT NULL,
  `created_by_id` int(10) unsigned DEFAULT NULL,
  `updated_by_id` int(10) unsigned DEFAULT NULL,
  `locale` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`id`),
  KEY `relances_documents_idx` (`document_id`,`locale`,`published_at`),
  KEY `relances_created_by_id_fk` (`created_by_id`),
  KEY `relances_updated_by_id_fk` (`updated_by_id`)
) **ENGINE=MyISAM AUTO_INCREMENT=18 DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;**

CREATE TABLE `relances_user_lnk` (
  `id` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `relance_id` int(10) unsigned DEFAULT NULL,
  `user_id` int(10) unsigned DEFAULT NULL,
  `relance_ord` double unsigned DEFAULT NULL,
  PRIMARY KEY (`id`),
  UNIQUE KEY `relances_user_lnk_uq` (`relance_id`,`user_id`),
  KEY `relances_user_lnk_fk` (`relance_id`),
  KEY `relances_user_lnk_ifk` (`user_id`),
  KEY `relances_user_lnk_oifk` (`relance_ord`),
  CONSTRAINT `relances_user_lnk_fk` FOREIGN KEY (`relance_id`) REFERENCES `relances` (`id`) ON DELETE CASCADE,
  CONSTRAINT `relances_user_lnk_ifk` FOREIGN KEY (`user_id`) REFERENCES `up_users` (`id`) ON DELETE CASCADE
) **ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;**

As you can see, the 'relances_user_lnk' is not with the same engine , not the same charset, and not the same collate. When i dropped the table and recreated it (mysql client), mysql refuses it : "(errno: 150 "Foreign key constraint is incorrectly formed")"

When i've modified the table creation, with **ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=latin1 COLLATE=latin1_swedish_ci;** , mysql accepted it, and now i can input my relations with the Strapi Content Manager.

**Solution: take in account the engines, charset and collate for the "lnk" table creation.**


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