feat(netbox): support Netbox v4.2

Fixes #8280
Fixes #7645
See Zammad#34699
See https://xcp-ng.org/forum/topic/10236/netbox-version-4-2-1-not-supported
See https://github.com/netbox-community/netbox/releases/tag/v4.2.0

Nothing to do because:
- Clusters: `site` is replaced by `scope` (a region, site, site group or
  location) but we don't auto-assign `site` on clusters.
- VMs: `site` field still exists. We don't assign it except for old versions
  where we use the cluster's `site`.
- Prefixes: `site` is also replaced by `scope` but prefixes are created
  manually.

CHANGELOG.unreleased.md

@@ -16,6 +16,7 @@
   - `/rest/v0/hosts` (PR [#8372](https://github.com/vatesfr/xen-orchestra/pull/8372))
   - `/rest/v0/hosts/<host-id>` (PR [#8372](https://github.com/vatesfr/xen-orchestra/pull/8372))
   - `/rest/v0/hosts/<host-id>/stats` (PR [#8372](https://github.com/vatesfr/xen-orchestra/pull/8372))
+- [Netbox] Support version 4.2.x
 
 ### Bug fixes
 
@@ -44,5 +45,6 @@
 - @xen-orchestra/rest-api minor
 - @xen-orchestra/xapi patch
 - xo-server patch
+- xo-server-netbox minor
 
 <!--packages-end-->

docs/docs/advanced.md

@@ -276,7 +276,7 @@ Synchronize your pools, VMs, network interfaces and IP addresses with your [Netb
 
 - `>= 2.10`
 - `3.x`
-- `< 4.2`
+- `< 4.3`
 
 :::tip
 For safety, XO will not synchronize your pools if it detects a Netbox version that is not supported. If you wish to change that behavior, edit you `xo-server` configuration like so:

packages/xo-server-netbox/src/index.js

@@ -16,7 +16,7 @@ import slugify from './slugify'
 
 const log = createLogger('xo:netbox')
 
-const SUPPORTED_VERSION = '>=2.10 <4.2'
+const SUPPORTED_VERSION = '>=2.10 <4.3'
 const CLUSTER_TYPE = 'XCP-ng Pool'
 const TYPES_WITH_UUID = ['virtualization.cluster', 'virtualization.virtualmachine', 'virtualization.vminterface']
 const CHUNK_SIZE = 100