Implement StatusEvent subclasses
Among Tor's event types the STATUS_* are the most expansively documented, having dozens of sub-specifications based on its StatusAction attribute.
Presently stem simply provides a StatusEvent class, leaving it to callers to make sense of its keyword_args. This is ok, but in an ideal world we'd have StatusEvent subclasses for each of the StatusAction types with attributes and validation reflecting their sub-specification.