Breaking change: Separate SKU-specific APIs into their own namespaces

[hpsin]

E.g. portal.HoloLens.StartMixedRealityCaptureAsync();
This makes using the portal object much simpler to use via Intellisense and clearly delineates which APIs work on which platform.

[hpsin]

#244 handles this request, and I've got about half of an implementation that creates a namespace off of the devicePortal object. We will be reaching out to the community for commentary on which version of namespacing (if any) they prefer.

[hpsin]

Proposed API taxonomy for the breaking change.

• Xbox
  -- Screenshot, XboxSettings, XboxLiveUsers (Surface Hub wants user management like this though), Fiddler (deprecated, I think?)
  -- XboxLiveSandbox – this one isn’t Xbox specific, so where should it go?
• IoT
  -- Lots of IoT specific APIs, as well as ActivateApp, GetApps, which should be redundant with Core APIs.
• MixedReality
  -- IPD settings, Controls, Thermals
  -- Mixed Reality Capture
• AppManagement
  -- Install/launch/delete apps
• System
  -- Remote Control (shutdown/reboot)
  -- Attached Devices
  -- SleepStudy
  -- Performance (e.g. all-up CPU usage)
  -- Power controls
  -- SetIsHttpsRequired – this is HL only right now, but could migrate.
• Network
  -- Get/set ipconfig/adapters/wifi settings
  -- NetworkMon would go here.
• FileExplorer
  -- All of the file explorer APIs + SMB share info (currently Xbox only ☹ )
• Debug
  -- Crashdumps, live dumps, WER reports.
• ETW
  -- Both WPR and live ETW.
• Client*
  -- ConnectAsync
  --- I think these could go on root instead. E.g. deviceportal.ConnectAsync rather than devicePortal.Client.ConnectAsync
• REST
  -- PutAsync(“/custom/path”)

So code would now look something like:

var portal = new DevicePortal(connectionInfo);
portal.ConnectAsync().Wait();
var apps = portal.AppManagement.GetAppsAsync().Wait();
portal.AppManagement.LaunchApp(apps[0]);