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).
This makes me nervous in an exception handler dealing with a failure in an error reporting module, especially when the exception we're catching has something to do with writing to this same file. Maybe the disk is full? Or failed? Or was a USB drive that got unplugged? Or we ran out of file handles? Or we don't have enough memory to do anything much? Could we return null here and write something like "could not attach log file" into the main report?