[Feature] Option to use an ordered set as history

[ToxicMushroom]

Currently you can sometimes have the issue described in #35
A setting to use an ordered set for saving the history could partially help remedy the worst effect of this issue (an ever growing un-searchable history).
But after looking at the code there seems to be quite a hard dependency on GTKListStore, so I'd understand not wanting to add this.

Further notes if interested:
When a duplicate song gets detected again, its position should then jump up to the top again.

This does kind of break the meaning of "history" so maybe when the set is used it should be called something else (I'm failing to come up with anything good at the moment)