Storage layout's partition IDs change upon snap refresh

[Christian Grabowski]

A user looking for support in the ~MAAS mattermost channel encountered an issue where they had a snap refresh from 3.4/stable to 3.4/edge, when this happened, the disk / partition IDs within machine storage layouts changes. It seems the underlying disk or partition has its id swapped with another existing one. Below is an example:

original:
  2 default_disks:
  3 - id: '385'
  4 name: disk0
  5 parent_disk_blkid: '385'
  6 ptable: GPT
  7 type: disk
  8 - device: '16340'
  9 id: disk0-part4
 10 number: '16340'
 11 parent_disk: '385'
 12 parent_disk_blkid: '385'
 13 size: '37199282176'
 14 type: partition
 15 - fstype: ext4
 16 id: 16340-format
 17 label: root
 18 parent_disk: '385'
 19 parent_disk_blkid: '385'
 20 type: format
 21 volume: '16340'
 22 - device: 16340-format
 23 id: 16340-mount
 24 parent_disk: '385'
 25 parent_disk_blkid: '385'
 26 path: /
 27 type: mount

refreshed:
  2 default_disks:
  3 - id: '385'
  4 name: disk0
  5 parent_disk_blkid: '385'
  6 ptable: GPT
  7 type: disk
  8 - device: '39252'
  9 id: disk0-part2
 10 number: '39252'
 11 parent_disk: '385'
 12 parent_disk_blkid: '385'
 13 size: '37199282176'
 14 type: partition
 15 - fstype: ext4
 16 id: 39252-format
 17 label: root
 18 parent_disk: '385'
 19 parent_disk_blkid: '385'
 20 type: format
 21 volume: '39252'
 22 - device: 39252-format
 23 id: 39252-mount
 24 parent_disk: '385'
 25 parent_disk_blkid: '385'
 26 path: /
 27 type: mount