Note creation through directional movement aka NOT A CURSOR

Or it is, if you want to consider it one.

This branch also has the integration test refactors.  Tests are now great to read and write and it enabled this chunk of code to be tested with somewhat complicated moves and assertions.

This branch also contains a selection fix.  Creating a note via keystroke 'c' was setting the 'selected' property of the part controller which had been changed to an alias that pointed to the selectionBox controller.  Setting a property that is an alias removes the relationship to the aliased property without throwing an error I guess?  It resulted in weird issues that broke the selection system.  There are regression tests that cover this issue as a byproduct of the user-creates-notes-with-movement feature.
{pitchNumber, absoluteTicks, duration} = note.getProperties('pitchNumber', 'absoluteTicks', 'duration')