Only suite:configuration emits full ua/runtime description

All other events emit only the uuid. Consumers should use the
suite:configuration event to connect a human-readable ua description with
a specific uuid.

This vastly reduces the amount of data transported by the test runner, while
not loosing any data _and_ clearing up possible ambiguity in having the
ua description emitted multiple times ("will this vary between events?")