During Port DFU-to-DFU re-enumeration, macOS deviceinterfaced daemon can
acquire the USB interface first, making idevicerestore time out waiting
for DFU reconnection.

Add experimental flag: --exclusive-usb that keeps deviceinterfaced from
claiming the USB device for the duration of the restore, by booting it
out or repeatedly terminating it when bootout is denied (SIP on), then
reloading and starting it again on exit.

idevicerestore itself does not need to run as root for this. Only the
launchctl subcommands that manage the system-domain deviceinterfaced
daemon (bootout, bootstrap, kickstart, kill) are elevated individually
via sudo, which may prompt for a password on the controlling terminal.
Read-only queries (print) are run unprivileged. Document how to allow
these specific commands via a scoped sudoers(5) NOPASSWD rule for
unattended use.

Co-authored-by: Nikias Bassen <nikias@gmx.li>

SourceBootObjectV4 ignored GlobalManifestPrefix and
GlobalManifestSuffix and always selected apticket.<DeviceClass>.im4m,
supplying the AP manifest when another manifest family was requested.

Use the requested path components and send FileDataDone when an
optional manifest is absent. Requests without these fields retain the
existing AP-ticket path.

  Add support for new data types and message types required by the macOS 27
  (build 26A5353q) restore protocol when restoring via DFU mode:

  - BootabilityBundleV2 (required): Updated bootability bundle handler
    to recognize both V1 and V2 IPSW directory prefixes. The V2 handler
    reuses the existing V1 cpio-over-connection wire protocol.

  - SourceBootObjectV5 (optional): Routes to the existing V4 handler
    which uses the same ImageName-based extract/personalize/stream flow.

  - DeviceRestoreInfoPreflight (optional): Handled as an empty-dict
    preflight acknowledgement, same as FirmwareUpdaterPreflight.

  - RestoreProtocol (optional, message type): Logged and acknowledged
    in the main message loop.

  Without BootabilityBundleV2 in SupportedDataTypes, the device's restored
  daemon fails the is_host_compatible check during DFU restore with:

    host/device compatibility check found that a message is missing
    or is not supported (required): BootabilityBundleV2
    CHECKPOINT FAILURE: This host version is unsupported.

  Tested: Erase restore of macOS 27.0 (26A5353q) via DFU on Macmini9,1
  (j274ap, M1) completes successfully.

e.g. emulated ones via ChefKiss Inferno