storage: Move and rename disk backend label checking
    
    Rather than have the Disk code having to use PARTED to determine if
    there's something on the device, let's use the virStorageBackendDeviceProbe.
    and only fallback to the PARTED probing if the BLKID code isn't built in.
    
    This will also provide a mechanism for the other current caller (File
    System Backend) to utilize a PARTED parsing algorithm in the event that
    BLKID isn't built in to at least see if *something* exists on the disk
    before blindly trying to use. The PARTED error checking will not find
    file system types, but if there is a partition table set on the device,
    it will at least cause a failure.
    
    Move virStorageBackendDiskValidLabel and virStorageBackendDiskFindLabel
    to storage_backend and rename/rework the code to fit the new model.
    
    Update the virsh.pod description to provide a more generic description
    of the process since we could now use either blkid or parted to find
    data on the target device.
    
    Signed-off-by: John Ferlan <jferlan@redhat.com>