fix(xo-web/VM/Advanced): fix 'not enough permission' error for super admins when attaching PCIs

[MathieuRA]

Description

Can be tested on the pool 172.16.210.83 with the VM MRA PCI.
On the host XCP XO 8.3.0 slave 2, the PCI Non-Volatile memory controller is ready to be attached to a VM.
Feel free to migrate the VM's VDI if you need to fully test the fix.
If you move the VM's VDI on the XOSTOR NVME SR, don't start the VM otherwise the VM will not start

Fixes Forum#9260

Checklist

• Commit
  • Title follows commit conventions
  • Reference the relevant issue (Fixes #007, See xoa-support#42, See https://...)
  • If bug fix, add Introduced by
• Changelog
  • If visible by XOA users, add changelog entry
  • Update "Packages to release" in CHANGELOG.unreleased.md
• PR
  • If UI changes, add screenshots
  • If not finished or not tested, open as Draft

[MelissaFrncJrg]

The VM start fails with the following error:

vm.start
{
  "id": "1b20c2ca-dc4e-717a-0940-7452b719a090",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "INTERNAL_ERROR",
  "params": [
    "xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\"))"
  ],
  "call": {
    "method": "VM.start",
    "params": [
      "OpaqueRef:0dc8626f-f85a-6164-7345-20b2d7597dd9",
      false,
      false
    ]
  },
  "message": "INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\")))",
  "name": "XapiError",
  "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\")))
    at Function.wrap (file:///home/mel/VATES/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at file:///home/mel/VATES/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

[MathieuRA]

The VM start fails with the following error:

vm.start
{
  "id": "1b20c2ca-dc4e-717a-0940-7452b719a090",
  "bypassMacAddressesCheck": false,
  "force": false
}
{
  "code": "INTERNAL_ERROR",
  "params": [
    "xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\"))"
  ],
  "call": {
    "method": "VM.start",
    "params": [
      "OpaqueRef:0dc8626f-f85a-6164-7345-20b2d7597dd9",
      false,
      false
    ]
  },
  "message": "INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\")))",
  "name": "XapiError",
  "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:01:00.1, Xenctrlext.Unix_error(30, \"1: Operation not permitted\")))
    at Function.wrap (file:///home/mel/VATES/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at file:///home/mel/VATES/xen-orchestra/packages/xen-api/transports/json-rpc.mjs:38:21
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:447:9)
    at process.callbackTrampoline (node:internal/async_hooks:130:17)"
}

The VM fail to start because of an issue in the host. Not due to the PR