Add Feature Tracking for Measure-Tools

[MikeNBentley]

Resolve Issue #980

Based off solutions on tree-widget package, add feature tracking to measure-tools. Now, users can pass their callback function onFeatureUsed to MeasureToolsUiItemsProvider to handle features being used. There is an usage example in the updated README.

(This information is also included in README but just put here for reference) The feature tracking message is now in format feature-[feature being used]-event-[event related to the feature]. This format should be easy enough for users to process and paste the message.

Current tracking features and respective are (will update more later!) (for detailed message, please again refer to updated README):

• Distance Measurement: Trigger, Cancel (for example we change to select mode or clear all measurements), Click on Start/End point of Distance

• Clear Measurements: Trigger

• Property Widget: When results are updated, when widget is empty

• Selection Set: While this is not essentially a feature. All measurements seem to base off a global selection set. Hence, changes to this selection set might prove useful for users, so feature tracking for Selection Set is added.

[bsy-nicholasw]

We already have feature tracking that all the tools call if subclasses provide Feature and it's called in the postInstall of the base tool. At some point in the past, the implementation did change a bit so the app would have to set it up by adding an event listener to FeatureTracking.onFeature.

At most this should just be providing a listener in the props to the UI provider that hooks up this event for the app, but it's also arguable that could also happen in MeasureTools.startup.

For the extra granularity in features, they should be added to our list of features in FeatureTracking, but who requested adding those for every point / property widget update?

[MikeNBentley]

We already have feature tracking that all the tools call if subclasses provide Feature and it's called in the postInstall of the base tool. At some point in the past, the implementation did change a bit so the app would have to set it up by adding an event listener to FeatureTracking.onFeature.

At most this should just be providing a listener in the props to the UI provider that hooks up this event for the app, but it's also arguable that could also happen in MeasureTools.startup.

For the extra granularity in features, they should be added to our list of features in FeatureTracking, but who requested adding those for every point / property widget update?

I will base off these ideas and make other PR. Thank you!