Humanreadable search

This is based on the #186. I refactored the parsing of the time input to use QRegexp directly and added a special query node for the time-querys because they are now not purely numeric anymore. 

To search for a track of exactly 90 seconds the following terms are equivalent.

90
90s
1m30
1m30s
1:30

searching for 62 seconds can be entered as

62
62s
1m2
1m2s
1m02s
1:2
I thought about that too. I would have gone with 'dur'. All the supported search terms correspond to the name of the tracktable column right now. I would like to keep this because it is an easy to understand and document rule