Handle generic object references in forms migrations

[AdrienClairembault]

Checklist before requesting a review

• I have performed a self-review of my code.
• I have added tests that prove my fix is effective or that my feature works.

Description

Formcreator questions may reference data from the generic objects plugin:

Since this plugin is replaced by native custom assets in GLPI 11, we must look for the migrated itemtype instead.

References

Internal support ticket: !39700

[AdrienClairembault]

Rebased to fix conflicts.

[cedric-anne]

Result will not be the same whether the genericobject migration has been processed or not.
The genericobject migration import the plugin items, import the related CommonDBConnexity items, but does not update foreign keys present in other objects classes. Maybe it should.

[AdrienClairembault]

Result will not be the same whether the genericobject migration has been processed or not.

I expect the generic object migration to be executed first in this case, at least it unlock the situation.

The genericobject migration import the plugin items, import the related CommonDBConnexity items, but does not update foreign keys present in other objects classes. Maybe it should.

Indeed, but it might not be easy to set up (can you do it for 11.0.2 ?)
I'd prefer merging this now and deal with this later, but it is clearly something to remember as the issue might happen for others features.

[AdrienClairembault]

I'll wait for #21709 to be merged before fixing conflitcs as it will conflict on the same test file again.

[AdrienClairembault]

Rebased to fix conflicts.

[cedric-anne]

I am working on a more global fix to handle update of foreign keys during the genericobject migration.

[AdrienClairembault]

Replaced by #21768