Strange order dependency between zoomTransformProperty and zoomScaleProperty

[pixelzoom]

assert.js:25 Uncaught Error: Assertion failed: space for units label is negative or zero
    at window.assertions.assertFunction (assert.js:25:13)
    at new RulerNode (RulerNode.js? [sm]:147:21)
    at createRulerNode (GORulerNode.ts:340:10)
    at GORulerNode.ts:136:22
    at TinyProperty.emit (TinyEmitter.ts:93:9)
    at DerivedProperty._notifyListeners (Property.ts:289:23)
    at DerivedProperty.set (Property.ts:223:14)
    at DerivedProperty.getDerivedPropertyListener (DerivedProperty.ts:131:13)
    at TinyProperty.emit (TinyEmitter.ts:93:9)
    at NumberProperty._notifyListeners (Property.ts:289:23)

To reproduce manually:

1. Run the sim with ?ea
2. Go to Lens screen
3. Pull a ruler out of toolbox
4. Press zoom-out (-) button
5. Press zoom-in (+) button. The assertion will fail.

[pixelzoom]

Scaling of rulers got messed up sometime since 1.1.0-dev.14 was published on 1/12/2022 @ 12:51. Their view length should not change when zooming in/out, only the scale on the ruler should change. But the view length of the ruler is now changing.

For example, here's the horizontal ruler initially:

... and after pressing the zoom-out button once:

[pixelzoom]

Bisecting, I isolated this bug to 9802b4f.

[pixelzoom]

As noted in the above commit:

    //TODO There's a strange order dependency between zoomTransformProperty and zoomScaleProperty. If
    // zoomScaleProperty is defined first, then zoomTransformProperty is incorrect, and rulers will be
    // messed up as in https://github.com/phetsims/geometric-optics/issues/295. This has something to
    // do with the fact both Properties call getAbsoluteZoomScale.

So there's more work to do here. And this is another good reason to reimplement model-view transforms in #277.

[pixelzoom]

Addressed in #277, closing.