(translate_why_removed_one) ensure we got the right reason

(testsuite) adapt to new URPM predictible behaviour

it was previously relying on the following fixed hash order:

$ perl -MData::Dumper -e 'warn Dumper [ keys {'rr1', 'rr1', 'rr2',
'rr2'} ]; \
warn Dumper [ keys {'bb1', 'bb1', 'bb2', 'bb2-1'} ]'
$VAR1 = [
          'rr2',
          'rr1'
        ];
$VAR1 = [
          'bb1',
          'bb2'
        ];

This fix is needed in cases where rpm's libdb changes. If the priority updates
happen to be installed in more than one transaction, the %post script in rpm
which deletes the old index files (/var/lib/rpm/__db.*) may happen at the
end of the first of those transactions. This causes the indexes to be
regenerated by the *old* db version and causes the second transaction to fail.

By ensuring the priority updates are handled in a single transaction, the
indexes will be recreated after the urpmi restart and will thus use the
correct, new libdb to create the indexes.

Patch and fix from Thierry Vignaud

it's also a huge speedup (saves 28% of time spent in testsuite)

this fixes urpmq defaulting to fuzzy mode (mga#2953)