zed: Use ID_MODEL instead of ID_BUS for autoreplace

[tonyhutter]

Motivation and Context

Fixes #13512

Description

We tried replacing an NVMe drive using autoreplace, only to see zed reject it with:

zed[27955]: zed_udev_monitor: /dev/nvme5n1 no devid source

This happened because ZED saw that ID_BUS was not set by udev for the NVMe drive, and thus didn't think it was "real drive".
A better option is to look for ID_MODEL instead. In testing, I saw ID_MODEL get set for a SATA drive (RHEL 7), SAS drive
(RHEL 8) and NVMe drive (RHEL 8), but not for a virtual drive on a VM.

How Has This Been Tested?

Tested autoreplace using an NVMe drive that had an ID_MODEL udev entry but not ID_BUS.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Performance enhancement (non-breaking change which improves efficiency)
• Code cleanup (non-breaking change which makes code smaller or more readable)
• Breaking change (fix or feature that would cause existing functionality to change)
• Library ABI change (libzfs, libzfs_core, libnvpair, libuutil and libzfsbootenv)
• Documentation (a change to man pages or other documentation)

Checklist:

• My code follows the OpenZFS code style requirements.
• I have updated the documentation accordingly.
• I have read the contributing document.
• I have added tests to cover my changes.
• I have run the ZFS Test Suite with this change applied.
• All commit messages are properly formatted and contain Signed-off-by.

[tonyhutter]

There's a tiny likelyhood that the ID_BUS check was filtering out some udev block device events that we didn't want (although I can't imagine what it would be). Just out of pure paranoia, I'm going to close this in favor of #13646 since it is theoretically safer.