Add failing spec for incorrect argument order

As exposed when using observe, for example, and asking to receive
notification before the change has occurred.
Stop passing beforeChange as token to aRCL API

This triggered issues downstream where the second argument is expected
to be the token, but was instead the before flag.
Merge pull request #29 from mczepiel/range-change-token

Stop passing beforeChange as token to aRCL API