mpu6000: add & check for the device_type on driver startup
mpu6000: add & check for the device_type on driver startup

Fixes the following case: a board that has several bus_options enabled,
and wants to start a specific device (eg mpu6000 -T 20608 start). In that
case the given device_type is never actually checked, and since the start
routine iterates over all bus_options, several can match, and thus start
multiple instances of the driver (note that the whoami check is performed
against the value provided with -T and thus the check will pass).

This happens on Pixracer (PX4_SPIDEV_MPU and PX4_SPIDEV_ICM_20608 are both
set).

jlecoeur/Firmware,mcgill-robotics/Firmware,PX4/Firmware,acfloria/Firmware,Aerotenna/Firmware,krbeverx/Firmware,acfloria/Firmware,mcgill-robotics/Firmware,mje-nz/PX4-Firmware,mje-nz/PX4-Firmware,mje-nz/PX4-Firmware,mje-nz/PX4-Firmware,jlecoeur/Firmware,krbeverx/Firmware,acfloria/Firmware,dagar/Firmware,Aerotenna/Firmware,mcgill-robotics/Firmware,mje-nz/PX4-Firmware,dagar/Firmware,PX4/Firmware,dagar/Firmware,jlecoeur/Firmware,PX4/Firmware,dagar/Firmware,Aerotenna/Firmware,dagar/Firmware,krbeverx/Firmware,mcgill-robotics/Firmware,Aerotenna/Firmware,mje-nz/PX4-Firmware,jlecoeur/Firmware,PX4/Firmware,acfloria/Firmware,dagar/Firmware,jlecoeur/Firmware,mcgill-robotics/Firmware,krbeverx/Firmware,krbeverx/Firmware,acfloria/Firmware,krbeverx/Firmware,dagar/Firmware,jlecoeur/Firmware,mje-nz/PX4-Firmware,mcgill-robotics/Firmware,mcgill-robotics/Firmware,Aerotenna/Firmware,acfloria/Firmware,jlecoeur/Firmware,PX4/Firmware,krbeverx/Firmware,acfloria/Firmware,Aerotenna/Firmware,jlecoeur/Firmware,Aerotenna/Firmware,PX4/Firmware,PX4/Firmware