Attach log file instead of appending it to description

If we don't have a log file we append the line "No log available" to
the description, otherwise we attach the log file to the jira issue.

Also don't show reporter dialog on taskbar (which otherwise shows up as question mark on Linux).
I'm sorry, maybe I'm being too picky, but I still don't see the point of this. Yes, there are two callers, but I think they need to do different things if something goes wrong while trying to create the log file. The main error report can add something to the summary of the Jira saying it failed to attach a log. I can't see where to put that message in the zip file case so maybe just do nothing there...or is it possible to create a zip entry without ever creating the file? Maybe actually name the file "missing error log" or something like that? Or maybe it does do some good to write something to the log we are failing to send...someone might get to look at it locally. But I don't see how things are improved by possibly returning...and attaching to the Jira or zip...a randomly-named empty file (assuming we succeed in creating that).

I suppose it's possible that we succeeded in writing some useful part of the log to the temp file before things went wrong. But we're dealing with edge cases of exceptional situations here...the main thing is not to crash in the error handler.