i have this in my development tree but i havent used it yet. idk bruh

when using api_latency during the websocket heartbeat jitter, it will
report 0.00. this resolves that by using the READY event by measuring
time from ident send

additionally, remove headers curl slist free since it would also free
the overarching slist, which isnt created by us. we can dirty it but i
would rather free it in the context that created it so its obvious that
its Not A Memory Leak:tm:

additionally, edit ping to use new abstractions and command declaration
facilities.  TODO: move interaction create event to somewhere else. this
spot isnt too good for it.