FIX / PDF export for assignable asset groups

[Mary-Clb]

• 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 !43643 & !45124
• This PR fixes PDF exports for assignable GLPI assets when group fields are loaded as arrays of IDs. The PDF plugin was still assuming that groups_id and groups_id_tech were always scalar values, while GLPI now loads these fields from glpi_groups_items as arrays for assignable items. As a result, group-related fields could be empty or incorrectly rendered in generated PDFs.
  The classes updated are the ones impacted beacause they correspond to assets implementing the AssignableItem feature.

Screenshots :

Before fix :

After fix :

[Rom1-B]

CHANGELOG please (always update it)

[stonebuzz]

Better 🙂

However, we now have a significant amount of duplicated code. We should refactor and consolidate these methods into a single unified implementation.

[Mary-Clb]

@stonebuzz can I send it to the client ?

[stonebuzz]

There’s something I’m not fully grasping in this PR.

In GLPI, an object can be assigned to a group using a one-to-one relationship (i.e., the object contains a groups_id or groups_id_tech column, for example in glpi_itilcategories).

Objects can also be assigned to multiple groups through an intermediate relation table, glpi_groups_items (cf: glpi_computers).

These objects rely on that relation table when they use the AssignableItem trait.

Here (unless I’m mistaken), we are only handling the first case.

[Mary-Clb]

following @stonebuzz comment :

getGroupName() now explicitly distinguishes the two group relationship cases you raised:

• Many-to-many ($item instanceof AssignableItemInterface, e.g. Computer, Monitor, Printer...) : queries glpi_groups_items directly, filtered by type (normal/tech), instead of implicitly relying on the conversion already done internally by the AssignableItem trait.
• One-to-one (direct groups_id/groups_id_tech column, e.g. ITILCategory) : unchanged.