Add source / destination on History and Network screens

[cliffhall]

Problem

On both the History and Network screens, it's not clear which direction a given entry traveled. That is, it's hard to tell which entries are client sent and which are server sent at a glance. I would use the terms request and response, except that in the case of Tasks, servers can request that clients run tasks and the client responds to queries about the task status, etc.

Solution

I propose a new dual-state badge client -> server / client <- server be placed at the top left of each entry in either screen. In addition to illustrating the direction of message travel, the two states would have different background colors, green or yellow, perhaps for quick recognition.

Caveat

Though the element for the badge will be shared and located in the same place on both entry cards, the method / input for determining the direction may be different.

• Network screen, there is already such an indicator in the TUI on v1.5/main, and it uses some property of the list entry entity to derive that.
• History screen, there may not be a specific property on the list entry entity, but there should be one established, and set when the server sent message is received and a list entry is instantiated from it, or when a client sent message is about to be sent and its list entry is instantiated.