feat(migration): add type renaming to resolve native asset name conflicts

[MyvTsv]

• I have performed a self-review of my code.
• I have added tests (when available) that prove my fix is effective or that my feature works.
• This change requires a documentation update.

Description

• It fixes !42658
• It is not possible to migrate an asset from the genericobject plugin if its name is similar to an asset in the GLPI core. This fix allows users to rename an asset so they can continue the migration.

Screenshots (if appropriate):

Conflict:

Migrate

[Rom1-B]

Does this apply to names that are too long? And CLI ?

[stonebuzz]

CLI compatibility would be a plus.

[stonebuzz]

At the time of renaming, it should also be ensured that the total length (PluginGenericObject + New name) does not exceed the maximum allowed size for MySQL table names.

[Rom1-B]

It works.
Could you add a check that alerts if the table name exceeds 64 characters?
In the CLI, add at least one check and a message to prompt renaming in the interface.

[Rom1-B]

We also need to add the case where the Fields plugin adds fields

[Rom1-B]

If applyPluginsTypeRename() catches an exception and returns early, renameType() still displays the success message. The failure needs to propagate so the success flash isn't shown.

[Rom1-B]

Suggested change

	self::applyTypeRename(
	$migration,
	$type_id,
	$old_name,
	$new_name,
	$old_itemtype,
	$new_itemtype,
	);
	try {
	self::applyTypeRename(
	$migration,
	$type_id,
	$old_name,
	$new_name,
	$old_itemtype,
	$new_itemtype,
	);
	} catch (RuntimeException $e) {
	Session::addMessageAfterRedirect($e->getMessage(), false, ERROR);
	return false;
	}

[Rom1-B]

maxlength = MAX_TYPE_NAME_LENGTH (25) limits the raw input, but getSystemName() replaces ALL numbers with words (a5555555 --> afivefivefivefivefivefivefive, 8 --> 29 characters). A name that is valid on the client side may exceed the server limit.

[MyvTsv]

I've added the system name that will be used after renaming, for clarity