Crud, aggregate and index compass tabs reacts to the `refresh-data` event that is triggered by operations that should not cause data to be reloaded.

For example:

• when a database or a collection is created or dropped there is no reason to reload documents in any of the tabs: if those are new the docs wont be affected until switching, if is the current db or collection it would make no sense to reload data from a non existing db or collection.
• when an index is added or dropped there is no need to reload anything except in the index tab. Although the queries execution could potentially be affected the data would not.
• when the query bar query changes there is no reason to reload the aggregation document in input as the input docs for a pipeline does not depend on the query

We should consider avoiding to trigger `refresh-data` in those cases and either replace it with a more specific event that would not cause unexpected behaviour (ie. `database-created`) or simply avoid triggering any event unless needed.