Adjusted the range parameter value to be a little easier to parse, fixes
Squashed commit of the following:

commit a00e8c36c714c75f395682f28eb0cde53f3b1714
Author: Joerg Sonnenberger <joerg@bec.de>
Date:   Tue Sep 17 15:03:13 2013 +0200

    Allow dojo/store/JsonRest to be more client-side cache friendly.

    At least Firefox and Chrome won't cache requests with Range header set
    nor do they like answers with Content-Range. Make it possible to provide
    the desired range by query parameter rangeParam and check for
    X-Content-Range as well.
Always return QueryResults from map and filter

Fixes #17681
Refs #16903.  Added Indonesian translation from IBM.

Added nls/id/ files and updated  nls locale boolean lists to include id.
Same level of translations as the ones provided for 1.9 in March 2013.
Do not execute dojo/on until DOM is ready

This ensures that the focusin/out feature detection operates
properly even when people do not follow best practices and put
their code in the <head> instead of before </body>.

Refs #17599.
Revert "Do not execute dojo/on until DOM is ready"

This reverts commit 08187b88273f09326e5ebc8ea03eecd592e7eaca.
fix regression introduced by #17155
Just use onfocusin as a detection test for focusin support

Due to various restrictions on what dojo/on can depend on,
and a desire to resolve this issue so that a release can be issued,
simply check for a matching event key on the has-test element.
This stops focusin/focusout from being used in WebKit and Blink
in lieu of event capturing, which is not ideal, but is not any
worse than what was happening before.

Refs #17599.
Add missing host-node and host-rhino rules to has.js

Fixes #17741.
Use has.add for config-useDeferredInstrumentation

This ensures that a default build works the same as an unbuilt
version of Dojo, while still allowing the configuration value
to be fixed during a build.

Fixes #17753.