Fix CSS grid feature detection in tests #416

Cell spanning tests were running in Safari despite it not supporting CSS
grid. The problem is that Safari CSSStyleDeclarations have a property for
grid-column (specifically, -webkit-grid-column) despite the CSS engine
ignoring such attributes.

This was fixed by switching to a platform specific check for CSS grid
(checking for the existence of -ms-grid-row). This means that ListView
will only use CSS grid in IE. This is probably what we want because the
ListView's use of CSS grid is based on IE 10/11's implementation. If other
browsers were to implement CSS grid, ListView would have be updated anyway
to make use of the latest CSS grid standard.
Fix ListViewEventsTests outside of IE #134
Fix ListViewAnimation2Test outside of IE #134

There were a few problems:
- ListView styles in unit test had to be updated to account for the
  default -200px padding (the test's styles assumed the default padding
  was 0).
- Our technique of using win-proxy to prevent margin collapsing between
  the win-surface and the win-groupheadercontainer does not work in
  Safari. Fixed this by taking advantage of Safari's
  -webkit-margin-collapse CSS attribute.
- When a group header was unvirtualized, the win-groupheadercontainer was
  collapsing causing all of the items to shift. The fix is to set the size
  of the scrolling dimension of the win-groupheadercontainers for inline
  headers (width for horizontal layouts, height for vertical layouts).
  This matches what the layouts do when using CSS grid.
Fix surface length outside of IE #134

win-surface needs to be inline-flex instead of inline-grid so that it
sizes to its content rather than to its parent. This matches the
display: inline-grid style found in IE.
Enable more ListView tests outside of IE #134
Upgrade Chrome and Firefox on Saucelabs
Truncate callstacks for Saucelabs