feat: Power Provisioning Support via DSX Max-Q

[zhaozhongn]

DSX Max-Q supports definition of CPU/GPU power profile and association of host machines with power profiles. Based on its global and external knowledge of power capacity and demands, it eventually calls the BMC proxy NICo provides to set dynamic power limit on machines.

When user is using NICo and Max-Q without other relevant software, the storyline is

1. User admin deploys NICo and Max-Q agent on the same control plane.
2. User admin defines and manages "power profiles" available for the site
3. User can optionally specify a power profile name when calling NICo REST API to allocate instance(s)
4. NICo will allocate instance(s) based on other requirements, once the machine is selected, NICo calls Max-Q to associate the machine with that power profile name
5. NICo may need to create / manage resource groups via Max-Q in the process
6. User can later modify power profile name via NICo for existing instances
7. User will primarily watch power provisioning dynamic stats via Max-Q interface. However, they need to at least be able to see the instance power profile name via NICo's instance REST API
8. Optionally, user may be able to see each instance's actual power limit (set by Max-Q calling NICo) and/or actual power usage (read out from BMC)