fix tests

For most tests, I simply updated them to remove explicit 0.6sp setting.

For keysig, the spacing change affects number of empty measures on a
system.  Meaning the line breaks occur in different places for this
versus 1.3, which is indeed a concern.  Even before this change, there
were already cases where 1.3 scores required more systems in 2.0 than
they used to.  On the other hand, the spacing of this test is consistent
with how 2.0 lays out scores when created from scratch..

Bottom line: I fixed the test to pass, but we also need to consider the
bigger reasons why 1.3 scores often take more space in 2.0.  I think
setting barNoteDistance to 0.60sp by default was masking some of these
problems, but was creating difficult-to-read scores in the process.