define better MVC for filtered data

[onursumer]

Currently, after a filter operation, filtered data is retrieved either from the diagram content or from the table content.

Define a better MVC where each component filters the same set of mutations, and other components update the view by listening to the single source of data.

[onursumer]

• [x] View components are initialized with the mutation data retrieved from MutationDataProxy within MutationDetailsController. Wrap this data with the new mutation data structure, where we perform filters, selections, highlights, etc.
• [x] MutationDataFilterController should be the only place where we update the state (filter, highlight, select) through the new mutation data structure
• [x] Each component controller should only read the state from the new mutation data structure.
• [ ] It may also be a good idea to merge the new mutation data structure with MutationCollection
• [x] Avoid any cyclic event firing: Possible solution is to avoid firing any event if the state remains same after a function call on the data structure.
• [x] Prevent double filtering (example: filtering the table with the search box also performs the same filtering with MutationDetailsTableController)
• [ ] Mutation3dController still needs to be simplified!