fix: ensure that affected entries are in order before comparing

[G-Rath]

While the spec recommends that affected entries be sorted in order, it's not required and the comparison algorithm explicitly sorts affected before comparing.

I'd originally not done this because the databases generally being consumed by the detector do follow the recommendation and I didn't want the extra complexity but now that we have semantic this is very easy