Bugzilla

The `ChangesActor` has an optimization to avoid firing events on changes unless there's evidence of a consumer for those events. 
Until a [call to `ChangesActor.allChanges()`](https://searchfox.org/mozilla-central/rev/040aa667f419932adf425d92c7438f03230ad96b/devtools/server/actors/changes.js#66,73,101-103,108-110) is made, no events will be fired that a client can listen to.

The intention for this optimization was to avoid needless event traffic unless the Changes panel was in view (it calls `allChanges()` once opened). 

However, other interested consumers of change events, other than the Changes panel, have sprung up and this subtle optimization caused trouble for them with inconsistent firing of events.

Therefore, we should remove this optimization which trips up other developers and always fire change events regardless of any previous method calls to the `ChangesActror`.

The `ChangesActor` has an optimization to avoid firing events on changes unless there's evidence of a consumer for those events. 
Until a [call to `ChangesActor.allChanges()`](https://searchfox.org/mozilla-central/rev/040aa667f419932adf425d92c7438f03230ad96b/devtools/server/actors/changes.js#66,73,101-103,108-110) is made, no events will be fired that a client can listen to.

The intention for this optimization was to avoid needless event traffic unless the Changes panel was in view (it calls `allChanges()` once opened). 

However, other interested consumers of change events have sprung up and this subtle optimization caused trouble for them with inconsistent firing of events.

Therefore, we should remove this optimization which trips up other developers and always fire change events regardless of any previous method calls to the `ChangesActror`.