Feat: rename oversized containers from their edit form

[Rom1-B]

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 !45901
• When a container's computed table name exceeds MySQL's 64-character limit, the plugin now disables it instead of crashing, and shows a rename form directly on the container's edit page.
• Submitting a shorter name renames the container and reactivates it; if a table with matching data already exists under that name (e.g. after a version migration), its data is preserved instead of being replaced by an empty table.
• plugins:fields:check_database now also reports container/item type pairs with no matching table, and tables with no matching container/item type pair.

Screenshots (if appropriate):

[stonebuzz]

preItemPurge() now skips every inactive container, not only oversized ones: purging an item attached to a manually disabled container leaves its rows behind in that container table (orphan data resurfacing if the container is re-enabled).

[stonebuzz]

If an orphan table is recovered for this container while a different table already exists under $new_table, GLPI's Migration::renameTable() silently returns for glpi_plugin_* tables (no exception). The container is then reactivated on the pre-existing $new_table, the recovered data stays in the orphan table, and the user still gets "existing data preserved". Reject the rename (or at least skip $data_preserved) when $DB->tableExists($new_table) and $new_table !== $old_table.

if ($new_table !== $old_table && $DB->tableExists($new_table)) {
    Session::AddMessageAfterRedirect(sprintf(__('Table %s already exists.', 'fields'), $new_table), false, ERROR);
    return false;
}