Walk the Metasys spaces and equipment trees without hitting deprecated endpoints

Documented steps

1. Confirm the server is Metasys 15.0 or later before using the tree endpoints; they were added in that release.
2. GET {base}/spaces/tree?depth=1 for the root of the spaces hierarchy. depth defaults to 1 and is capped at 5; depth=0 returns only the root node.
3. GET {base}/spaces/tree/{spaceId}?depth=2 to expand a subtree beneath a specific space.
4. GET {base}/equipment/tree?depth=1 for equipment. depth defaults to 1; depth=-1 requests the entire tree; the docs recommend 1 to 2 in normal use.
5. Add excludeServed=true on the equipment tree to omit equipment that is currently serving another equipment or space, which flattens duplicated branches.
6. GET {base}/equipment/tree/{objectId} to expand an equipment subtree; the root may be an equipment instance or a folder. The response is {self, items[]} where each item is an equipmentTreeFolder or an equipmentTreeEquipment.
7. GET {base}/spaces/{spaceId}/servingEquipment (paged via page, pageSize, sort) for the equipment serving a space.
8. GET {base}/equipment/{equipmentId}/servedEquipment for downstream equipment, and GET {base}/equipment/{equipmentId}/upstreamEquipment for the full upstream chain.
9. Migrate any existing code off the deprecated endpoints: GET /spaces, GET /spaces/{spaceId}/spaces, GET /equipment, GET /equipment/{equipmentId}/equipment, and GET /spaces/{spaceId}/equipment.
10. Reference: https://jci-metasys.github.io/api-landing/api/v6-16 (Metasys REST API, 'Version 6 for 16.0', OpenAPI 3.0.3). Doc set index: https://jci-metasys.github.io/api-landing/ | changelog: https://jci-metasys.github.io/api-landing/guides/api-changelog/ | version support: https://jci-metasys.github.io/api-landing/guides/version-support-matrix/ | polling and streaming limits: https://jci-metasys.github.io/api-landing/guides/attribute-access-guidelines/