Decouple data events from display classes

Some of the display classes (AbstractImageDisplay, SwingImageDisplay) listen to data events and update their views. This is sort of backwards and poorly coupled.

Make views listen for data events and change their state appropriately. They should generate view events. Displays should listen for view events and update their state accordingly.

Migrated-From: http://trac.imagej.net/ticket/884

Start by reading AbstractImageDisplay and SwingImageDisplay to trace how they currently listen for data events and update views. Then locate the related view and display event flow. Done means views handle data events and emit view events, while displays respond to those view events without directly coupling to data events.

Written by the indexing model from the issue text.