Add OpenZMS-in-RDZ support

Add support for "inner" OpenZMS experiments to allocate their own test radios and spectrum from POWDER-RDZ.

Design discussion: https://docs.google.com/presentation/d/1OA9GiPlxEj7dGYFYPj1ya_gsFt0wSpLK5b0TgvlI7R0/edit#slide=id.g2f8fbf8309c_0_5

Phase 1 tasks:

• Legacy POWDER spectrum reservations are pushed to outer OpenZMS as “grant claims”
• OpenZMS grant scheduler/APIs handle new grant claim cases
• OpenZMS grant APIs expand to handle grant claims
• Test
• When inner OpenZMS POWDER-RDZ experiments are created, if swapper does not have account on root OpenZMS, one is created with “viewer” permission in the “powder” element
  • This is for now a per-experiment user, with a standard random password
  • User account is deleted when experiment terminates
• Test
• Add shared vlan support to OpenZMS profile
• Add shared vlan support to select RAN profiles that connect RAN/spectrum resources to an OpenZMS experiment over shared vlan
  • These profiles then "donate" their resources to the inner OpenZMS
  • The inner OpenZMS is automatically populated with these resources
  • This should (optionally?) include inline monitor data for connected radios

Phase 2 tasks:

• Synch’ing resources (using TBD code in https://gitlab.flux.utah.edu/openzms/zms-client-py)
• Getting monitor Observations (using TBD code in https://gitlab.flux.utah.edu/openzms/zms-client-py)
• Handling violations (TBD)