Change reload task failed log appender xml file to use same format as appender file for "reload aborted"

[mountaindude]

Is your feature request related to a problem? Please describe.
Right now "reload failed" and "reload aborted" use two slightly different mechanisms for triggering in the XML log appender files.

"Reload aborted" generates a UDP message like this:
/scheduler-reload-aborted/;%hostname;%property{TaskName};%property{AppName};%property{User};%property{TaskId};%property{AppId};%date;%level%property{ExecutionId};%message

"Reload failed" generates a message like this:
%hostname;%property{TaskName};%property{AppName};%property{User};%property{TaskId};%property{AppId};%date;%level%property{ExecutionId};%message

This is for historical reasons - when Butler was created "reload failed" was the only message, but as there was a need to detect different patterns in the log files (and send different UDP messages!), the first field in the UDP message was designated as an identifier field, telling what kind of event the message contained.

Describe the solution you'd like

1. Make "reload failed" UDP message look like this:
   /scheduler-reload-failed/;%hostname;%property{TaskName};%property{AppName};%property{User};%property{TaskId};%property{AppId};%date;%level%property{ExecutionId};%message
2. Keep the old format for "reload failed" UDP messages as the default one, if there is no match on the first field of the message. This will minimize the impact for systems that use the older UDP message format.

[mountaindude]

Included in coming 5.0 release.