Improve json logging pipeline error reporting

[robbavey]

#18435 described an issue where an issue with a plugin was difficult to track down, due to lack of information about where the issue originated:

Nov 17 16:58:15 SYSLOG03 logstash[6779]: {"level":"WARN","loggerName":"logstash.filters.mutate","timeMillis":1763398695072,"thread":"[sys_win_server]>worker59","logEvent":{"message":"Exception caught while applying mutate filter","exception":"invalid value for BigDecimal(): \"error\""}}

as opposed to:

[2025-11-17T22:06:31,388][WARN ][logstash.filters.mutate  ][pipeline1][b801eb4536ebedf6dffba66f748c482646d373b6e624f613789bb50303ada97d] Exception caught while applying mutate filter {:exception=>"invalid value for BigDecimal(): \"error\""}

Note the missing pipeline id "pipeline1" and plugin id "b801eb4536ebedf6dffba66f748c482646d373b6e624f613789bb50303ada97d" from the json log entry