Rating control fails to instantiate inside the wwahost, Fixes #347
Clean up our build excludes.
Make private SeZo contract public.

Closes #341
Merge pull request #348 from spankyj/master

Fix .gitignore to ignore bld directories.
Replace usage of DOMNodeInserted in Rating with a node-inserted css animation event (more reliable). Closes #298.
Fix #127: Get Tooltip tests running in all browsers

Most of the problems stemmed from WWA/IE implementing pointer events while
other browsers implement touch events. The only touch events that seem to
be implemented consistently are:
  - touchstart
  - touchend
  - touchmove

Tooltip relies on pointerover and pointerout for:
  - Showing a tooltip when the user presses and holds on a tooltip element
  - Showing a tooltip when the user hovers their finger onto a tooltip
    element
  - Hiding a tooltip when the user hovers their finger off of a tooltip
    element

There aren't any touch event equivalents for pointerover or pointerout. So
the first scenario was achieved in other browsers by also having
pointerdown (touchstart) show a tooltip. There isn't a good way to
implement the other 2 scenarios without pointerover/out so the other 2
scenarios do not work in other browsers. We are okay with this.

The unit tests which fired pointerover/out had to be modified to fire
alternative events in browsers that don't have pointer events.

--

When a tooltip is triggered, the control notes which input method
triggered the tooltip (_showTrigger). Before this change, when multiple
input methods triggered a tooltip, the control remembered the last method.
This was changed slightly so that it remembers the first method instead.

--

Our translation table used touchleave as the touch equivalent of
pointerout. Because touchleave has different semantics than pointerout and
nobody is currently relying on pointerout mapping to touchleave,
pointerout no longer maps to touchleave. When somebody needs pointerout,
we can think more about the appropriate touch equivalent.

--

Most of the other changes were around adjusting the unit test assertions
to account for slight differences in the return values of the CSS APIs of
the browsers.
Finish removing global WinJS references.
This change fixes a few things to make SeZo work right:
- The SeZo wouldn't zoom past the initial view outside of IE. The problem came from us determining the max scroll location of the listview by using the canvas, which wasn't reliable. I've switched this to use scrollWidth/height instead (both for SeZo, and in another spot for Drag and Drop, which fixes a cross platform DnD issue there too)
- The Layout wasn't measuring a couple layout configurations properly. There were two things missing:
1) We didn't add the noCSSGrid class to the measuring surface, so things weren't getting all the right styles
2) We were neglecting to add the header element before the item element in certain list layout measures, which was important to get the right numbers (it would work with CSS grid since we had exisiting code to do just that by changing the CSS row+column of the header and item)
3) We weren't disabling itemsBlocks in ListLayout, so Firefox wasn't rendering right
- There was a floating point error in Chrome. I've made that unit test check for a range instead of an exact value
- Changed the helper function that generates listviews for the sezo tests to make sure all the necessary styles are added to the containers and items being generated
Fix #350: Rating & Toggle tests hang in WWA
Enable JSHint rule to detect trailing whitespace.
Enable more JSHint checks.
Fix JSHint regressions in master.
Create single file version of WinJS.
Break the build when we regress JSHint.