fix(migration): table rename exceeds table name length limit

[MyvTsv]

Checklist before requesting a review

Please delete options that are not relevant.

• 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.
• I have updated the CHANGELOG with a short functional description of the fix or new feature.
• This change requires a documentation update.

Description

• It fixes !45001
• The migration of the "fields" plugin did not work if the container name was too long

Screenshots (if appropriate):

[2026-07-01 09:16:09] glpi.CRITICAL:   *** Uncaught PHP Exception RuntimeException: "MySQL query error: Incorrect table name 'glpi_plugin_fields_glpicustomassetvideoprojecteurassetfivesixnineeighttwosevensixzerosixes' (1103) in SQL query "CREATE TABLE IF NOT EXISTS `glpi_plugin_fields_glpicustomassetvideoprojecteurassetfivesixnineeighttwosevensixzerosixes` (
                  `id`                               INT          unsigned NOT NULL auto_increment,
                  `items_id`                         INT          unsigned NOT NULL,
                  `itemtype`                         VARCHAR(255) DEFAULT 'Glpi\\CustomAsset\\videoprojecteurAsset',
                  `plugin_fields_containers_id`      INT          unsigned NOT NULL DEFAULT 1,
                  PRIMARY KEY                        (`id`),
                  UNIQUE INDEX `itemtype_item_container`
                     (`itemtype`, `items_id`, `plugin_fields_containers_id`)
               ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci ROW_FORMAT=DYNAMIC;"." at DBmysql.php line 416
  Backtrace :
  ./src/DBmysql.php:416                              
  ...fivesixnineeighttwosevensixzerosix.class.php:31 DBmysql->doQuery()
  ./plugins/fields/inc/container.class.php:764       PluginFieldsGlpicustomassetvideoprojecteurassetfivesixnineeighttwosevensixzerosix::install()
  ./plugins/fields/inc/container.class.php:476       PluginFieldsContainer::create()
  ./plugins/fields/hook.php:90                       PluginFieldsContainer::installUserData()
  ./src/Plugin.php:1249                              plugin_fields_install()
  :                                                  Plugin->install()
  ./src/Glpi/Marketplace/Controller.php:710          call_user_func()
  ./src/Glpi/Marketplace/Controller.php:600          Glpi\Marketplace\Controller->setPluginState()
  ./ajax/marketplace.php:62                          Glpi\Marketplace\Controller->installPlugin()
  ...Glpi/Controller/LegacyFileLoadController.php:64 require()
  ./vendor/symfony/http-kernel/HttpKernel.php:181    Glpi\Controller\LegacyFileLoadController->__invoke()
  ./vendor/symfony/http-kernel/HttpKernel.php:76     Symfony\Component\HttpKernel\HttpKernel->handleRaw()
  ./vendor/symfony/http-kernel/Kernel.php:208        Symfony\Component\HttpKernel\HttpKernel->handle()
  ./public/index.php:71                              Symfony\Component\HttpKernel\Kernel->handle()

[Rom1-B]

Please rebase

[stonebuzz]

Suggested change

$container['label'] = $new_name;

setContainerName overwrites the human-readable label with the truncated system name. After migration, affected containers would display the internal machine name (e.g. verylongcontainernamef) instead of the original descriptive label. Only name needs to be truncated; label should remain the original value.

[stonebuzz]

Suggested change

	$container_obj->update($container);
	return $container_obj->update($container);

return if update process failed or not

[stonebuzz]

If setContainerName produces an empty name (edge case where even a 1-char system name yields a table name exceeding 64 chars) or if prepareInputForUpdate rejects the input, the update silently fails and the migration returns true.

[stonebuzz]

Suggested change

	__('Container name is too long for database', 'fields'),
	__('Container name is invalid or too long for database', 'fields'),