Revise design of dual-endpoint events

[rmarx]

Currently, we have some events that are used both for indicating changes in the local as well as the remote endpoint. An example is parameters_set, which logs both connection params we set locally, as the ones we get from the other side. parameters_set uses an "owner" field to disambiguate between these two cases.

However, other events with similar purpose, like connection_id_updated, use another approach (src_ vs dst_ prefixes). We should decide on a singular consistent approach (currently leaning towards "owner" field myself, as it is the most flexible)

[LPardue]

Is this still relevant?

[rmarx]

Given that there have been no further complaints/remarks on this and imo the split approach is clear enough, closing without action for now.