[Lainow]

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 !46820
• Here is a brief description of what this PR does

Brings back the Formcreator "email followup" per actor, lost by the forms migration.

• New "Email followup" destination field: one toggle per actor source (requesters, observers, assignees). A person found only by disabled sources gets no followup.
• New plugins:advancedforms:import-formcreator-actors-notification command to import the Formcreator settings (--dry-run, --force). Imported destinations are skipped by the next runs, so manual changes are kept.

Screenshots (if appropriate):

[RomainLvr]

Looks solid overall: the migrated form lookup (uuid5), name-based destination matching, HasFieldWithQuestionId on roles, _from_import, and the delegation handling all check out against core. A few remarks:

1. muteActorsInInput relies on a core internal. Core ITILActorField::addActorToInput() appends _notif entries without the template lines, while CommonITILObject pairs actors and _notif by the same key. With a template, core is already misaligned. The plugin re-indexes on $line, which fixes this, but only when it mutes someone ($has_changes). So the behavior depends on whether an actor is muted. The real fix belongs in core (index _notif like the actors); worth a separate core PR.
2. Duplicated logic. getSources() and getPersons() repeat the same SPECIFIC_VALUES / SPECIFIC_ANSWERS / strategy-level branching. Resolving persons from the sources already computed would remove about 80 lines from a 735-line file.
3. DOM hack in the Twig template. Moving the ? helper into the core label via :scope > div > label.form-label will break silently if the core markup changes. Acceptable without an extension point, but an E2E assertion on the helper would catch it.
4. Command storage in glpi_configs. It adds one destination_<id> row per imported destination. Fine for a one-shot command, and uninstall cleans the context, but keep it in mind for instances with thousands of destinations.
5. Minor: getPersons() calls strategy->getITILActors() again after the core actor field already did, so it runs twice per submission. Negligible today.

None of these are blocking; 1 and 2 are the ones I'd address.