[WARP Telemetry] Work around platform issues

Work around issues in platform which manifest as bugs or
latency issues when attempting to visualize telemetry
from the WARP Server. Specifically:

* Handle the possibility that there is no matching
  representation for an object from EditRepresenter.
* Don't attempt to look up colon-separated domain object
  identifiers from persistence. This is a workaround to
  avoid latency issues from excessive persistence calls;
  filed WTD-659 to improve this solution.

Changes made to support resolution of WTD-644.

platform/commonUI/edit/src/EditRepresenter.js

@@ -73,7 +73,7 @@ define(
             // Handle a specific representation of a specific domain object
             function represent(representation, representedObject) {
                 // Track the key, to know which view configuration to save to.
-                key = representation.key;
+                key = (representation || {}).key;
                 // Track the represented object
                 domainObject = representedObject;