udisksd erroneously logs about LUKS when manipulating VeraCrypt volume

E.g. I see Unlocked LUKS device /dev/loop1 as /dev/dm-0 after unlocking a VeraCrypt volume.

If this problem is specific to the backported version of our patches, well, forget it and reject this ticket.
If this problem is also present in the version we’ve upstreamed, then we should fix that.

Parent Task: #14468

Original created by @intrigeri on 15950 (Redmine)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information