1129817 - prepend process id and thread id if line is split

By including a unique identifier, it is possible to separate logs that are generated at the same time.

 [Bugzilla-1129817](https://bugzilla.redhat.com/show_bug.cgi?id=1129817)
I did some more experiments with longer max lengths, and I found that this problem does only occur if the thread id lands in the max length. I set it to 45, and these logs resulted:

```
Sep 18 10:29:05 notepad pulp: randy:INFO: This is a'OK
Sep 18 10:29:05 notepad pulp: randy:INFO: 54
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)This 
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)is mu
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)ch to
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)o lon
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)g, an
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)d wil
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)l go 
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)over 
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)the t
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)hresh
Sep 18 10:29:05 notepad pulp: randy:INFO: (4704-139783988725504)old.
```

So perhaps you are correct about it only being a problem with unreasonably small max lengths. Each of these messages is cut exactly at 45 characters, so they are correct.

It would be nice if we didn't include the thread id on single thread processes since it's so long.