Better granularity for edit events

[dkwon17]

In both of these scenarios:

1. User edits a java file for 10 minutes
2. User edits a java file for 1 minute, gets coffee for 8 minutes, comes back and edits a java file for 1 minute

there is only one edit workspace in che event sent to Woopra, even though the user in scenario 1 edits their Java file for a longer period of time compared to scenario 2.

Only one event is sent to Woopra in both situations because currently the telemetry plugin prevents two events with the same properties from being sent back to back:

devworkspace-telemetry-woopra-plugin/src/main/java/com/redhat/devworkspace/services/telemetry/woopra/AnalyticsManager.java

Line 332 in d3b37c6

if (!force && areEventsEqual(event, properties)) {

For better granularity, it would make sense for scenario 1 to cause more edit workspace in che events than scenario 2.

Some possible solutions are:

1. remove the if statement above to allow back to back edit events editing a file of the same language (ie Java, Python etc.)
2. remove the if statement above and increase/decrease the debounce time to adjust how often edit events are sent