[commhistory-daemon] Use x-commhistory-event-id in tp sent message headers

Clients may set that field if the outgoing message event already exists
or was created externally to prevent commhistory-daemon from generating
a duplicate event.

Currently, existing events are mostly ignored in the send handler; it
may later be useful to update their sending status in some way.