spatial awareness interfaces changes (more feature focused)

[Yoyozilla]

Overview

The Spatial Awareness System interface has too much of a burden for understanding the types of data a spatial observer may provide.

Similarly, putting a requirement on all observers to implement properties and methods, whether or not the type of data is provided, is not reasonable.

To resolve these issues, the IMixedRealitySpatialAwarenessSystem interface will be trimmed to provide only the core requirements for the system. Additionally, the IMixedRealitySpatialAwarenessObserver interface will be reduced to the essential components of an observer (ex: status, update interval, etc) with support for meshes, surface planes and other future types of data to be housed in data specific interfaces (ex: IMixedRealitySpatialAwarenessMeshObserver).

Enabling support for an observer that may return multiple types of data is critical as we should not require duplication of code or data synchronization issues in these scenarios.

Requirements

• Spatial Awareness interfaces are to become more feature / task focused
• Existing concrete implementations are updated to use one or more of the interfaces
• Client code can access / control aspects of the observers as appropriate
• Existing client code (ex: demo scripts) should experience minimal breaking changes

Acceptance Criteria

• Interfaces define the minimal set of properties and methods to provide the feature
• Existing demo script continues to function as expected