Make the return values of Client.transport_query() more Pythonic

[mgeier]

I want to rename transport_query() to transport_query_struct() to still have a low-overhead way to get the information, which might probably even be somewhat realtime safe.

Any suggestions for a better name?

Then I want to implement a new transport_query() method which calls the old transport_query_struct() and prepares the results to be nicer to handle:

• Create a jack.TransportState class to wrap the "state" integer
  • return an instance of this class from transport_query()
  • change the module constants (e.g. jack.ROLLING) to instances of this class
• Convert the fields from the jack_position_t struct into a Python dict that only contains the valid information

[Vampouille]

transport_query_struct() is a good name for me. It would be nice to have a dict with only valid fields.