Support installing on disk by id, uuid or path

1. Proposed title of this feature request
Support installing on disk by id, uuid or path
2. What is the nature and description of the request?

Currently, when doing the installation you can select the installation disks with different rootDeviceHints. Like name, serialnumber, etc:
https://github.com/metal3-io/baremetal-operator/blob/main/docs/api.md#rootdevicehints
but you cannot use any /dev/by-*  (by-id, by-uuid, by-path).

3. Why does the customer need this? (List the business requirements here)
Selecting the root disk by PCI path preferred compared to other methods becase:

• The deviceName is not stable the same way that the pci path is.
  deviceName can change in unpredictable ways e.g. when a BMC virtual disk is connected
• hctl suffers from a similar issue
• model etc are not guarenteed to give a unique and predictable result
• serialNumber and wwn are tricky to use since these methods first require a step where these are discovered.
  Selecting the root device by PCI path doesn't suffer from the drawback listed above.

The Assisted Installer discovery (Agent), actually, discovers all these ids:

- bootable: true
      byID: /dev/disk/by-id/wwn-0x6f4027xxxx326a9a1
      byPath: /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0
      driveType: HDD
      hctl: "1:2:0:0"
      id: /dev/disk/by-id/wwn-0x6f4027xxxx326a9a1       installationEligibility:
        eligible: true
        notEligibleReasons: []
      ioPerf: {}
      model: PERC_H330_Mini
      name: sdc
      path: /dev/sdc
      serial: 6f40270XXXXX6a9a1
      sizeBytes: 959656755200 

but cannot be selected for the installation.
Selecting disks by-* is also supported by other components like LocalStorage/ODF, so, the same kind of id is used in all the components about selecting disks.

4. List any affected packages or components.
BMH, Assisted Installer and ZTP