With the renaming of Fluid template files to `.fluid.html/text`
the EXT:linkvalidator mail construction was not able to perform
a proper lookup, fell back to the default template in such a
case, which ultimately lead to the task not running in CLI
context beccause a FlashMessage was emitted.
The EXT:linkvalidator `ValidatorTask` performed some runtime dynamic
adjustments to its own object in case of validation issues.
Specifically, if multiple email are comma separated instead of
newline separated and if a task template file does not exist.
If any of these two changes occured, the task object was
previously automatically rewritten. This no longer works
with the new TCA-based scheduler tasks introduced in
patches #107588 and #98453 due two two things:
1.) The `SchedulerTaskPersistenceValidator` prevents changes
to any task currently marked as running
2.) Additionally, the incoming field data array requires
all metadata present from the TCA data structure, not
just the `$task` object.
Additionally, the logic is flawed because in CLI context,
a missing backend user context will not properly initialize
FlashMessages to be persisted in the CLI BE_USER object,
because it is lacking session storage (`UserSessionManager`).
Error messages were also not displayed because a wrong XLF
file was referenced in CLI context.
Instead of adding more workarounds to this kind of setup,
the whole "update task object" logic is now removed. The
runtime validation changes will just be applied dynamically
each time.