make staticHasFeatures support non-booleans

[bill]

Some of the has() tests in dojo return numbers, rather than truthy values (true/false or 0/1). For example, has("ie") returns 6, 7, 8, or 9. has("...") for other browsers also return numbers.

staticHasFeatures cannot be used to optimize code branches with these has() references because even with a profile like:

staticHasFeatures:{
	chrome: undefined,
	mozilla: undefined,
	ie: 7
}

It will strangely replace has("ie") with 1 instead of 7.

[Rawld Gill]

See also #14792 which has a test case.

[Rawld Gill]

In [28541]:

improved static has processing; removed some cruft discovered while doing the work; fixes #14286; !strict