When using scan or lookup match function on tracks that have been previously tagged by Picard, and which have both a MusicBrainz DiscID tag and Release tag set, Picard ignores the discID tag when selecting from available matching releases and selects an incorrect release (overriding the correct release tag).

This happens whether or not "Ignore MBIDs when loading new files" is set.

For example, I've previously ripped and tagged tracks from this disc and release:

https://musicbrainz.org/cdtoc/ufzi4jFR6PuY2MDSE1WXx8oX2Gc-
https://musicbrainz.org/release/4a5a5055-db42-4d1c-a84a-16242ba6280e

There are multiple similar releases that match this CD TOC. When dragging these tracks into Picard, it incorrectly overrides the matching release with one that is similar but has no discIDs associated:

https://musicbrainz.org/release/a2a62dee-b38e-44ff-8c58-608efa30f955

BUG: Picard selects the release without a matching discID instead of the release with a matching discID.
BUG: PIcard overrides a matching release identifier with another matching release identifier. Picard should not replace an existing matching release identifier unless the new identifier is a better match.