If there is only one script present, it will be ued right away. Only if there are several present for the current tenant, the user can pick which
should be used. This way, a script will be automatically used everywhere if only one exists. If the script is optional, a second and empty
script can be provided.

…-scripting-3

The other load gets triggered way to often (for each find etc.)

Although currently only available to the system tenant, we plan on making the scripting API
safe in terms of sandboxing so that normal users could provide scripts as well.

Also adds a word of caution for others to maintain the sort
order.

We probably only want one event instead of one event per job type,
as the internal types are not that easy to guess.

This is mainly used for debugging purposes

…d AfterLoadEvent

…cireum/sirius-biz into feature/aha/import-scripting-3