fix(ticket): auto-assign tech with ITIL category launch rule

[MyvTsv]

• I have read the CONTRIBUTING document.
• I have performed a self-review of my code.
• I have added tests that prove my fix is effective or that my feature works.
• This change requires a documentation update.

Description

• It fixes !37648
• If a technician group or technician is assigned to a ticket via the category, the rules that target this field are not executed, as the rules are executed before the actor field is set by the category.

Screenshots (if appropriate):

Rule:

ITILCategory:

[stonebuzz]

seems good for me, can you add test ?

[MyvTsv]

It's good for customer

[stonebuzz]

@MyvTsv can fix lint

[cedric-anne]

This changes the behaviour of GLPI.
First, the auto assign was acting as a fallback. It was assigning tech/group only if none was already assigned. It means that it was not triggered, for instance, if a technician was added by a rule.
Second, it was possible to assign a tech based on a category defined by the rules. Now it will not be possible to do it anymore.
And then, it will change the behaviour of rules based on the assigned technician, and it may produce unexpected results, depending on the purpose of the corresponding rule.

I am not sure we should change it. @orthagh, your opinion?

[MyvTsv]

@orthagh
I tried the problem again on my side and this is what happened:

I assign a responsible group to a category and create a ticket rule with the group as a trigger that assigns that same group as an observer.

I create a ticket manually without using formcreator, I assign the category to the ticket and the group assigned to the category is assigned as technician. However, this same group is not the ticket's observer, which should be the case according to the rule.

If I create the same ticket, but manually assign the technician group without using the automatic assignment via the category, the rule is activated correctly, and the group also becomes the ticket observer.