thunderbolt: Use both locations for multi controller entry validation
thunderbolt: Use both locations for multi controller entry validation

Since the multi controller entry is part of the DROM and its place is
not fixed, it is possible (however unlikely) that the locations between
controller and the image are different. One scenario is that the new
image has typo in device or vendor name string fixed which could cause
the offset to be different.

To handle this case properly we need to read multi controller locations
of both controller and image separately, read their values and then
compare them against each other.

Signed-off-by: Mika Westerberg <afb75201fb002d7fdd2b0b231e006999e00db8a9@linux.intel.com>

vathpela/fwupd,vathpela/fwupd,fwupd/fwupd,hughsie/fwupd,hughsie/fwupd,hughsie/fwupd,fwupd/fwupd,hughsie/fwupd,fwupd/fwupd,vathpela/fwupd,fwupd/fwupd,vathpela/fwupd