Create angular-winjs.js

Shim layer which facilitates usage of WinJS UI controls in an Angular Windows application. It achieves this by creating directives for the various controls which allow them to show up in Angular markup like:

    <win-list-view item-data-source="mydata">
      <win-item-template>Hi: {{item.data.name}}</win-item-template>
    </win-list-view>

The various controls which are supported are:

* WinJS.UI.AppBar: <win-app-bar>
* WinJS.UI.AppBarCommand: <win-app-bar-command>
* WinJS.UI.BackButton: <win-back-button>
* WinJS.UI.DatePicker: <win-date-picker>
* WinJS.UI.FlipView: <win-flip-view>
  * Note: expects a child <win-item-template>
* WinJS.UI.Flyout: <win-flyout>
* WinJS.UI.Hub: <win-hub>
* WinJS.UI.HubSection: <win-hub-section>
* WinJS.UI.ItemContainer: <win-item-container>
* WinJS.UI.ListView: <win-list-view>
  * Note: expects a child <win-item-template>, and optionally <win-group-header-template> and/or one of the layouts like <win-grid-layout>
* WinJS.UI.Menu: <win-menu>
* WinJS.UI.MenuCommand: <win-menu-command>
* WinJS.UI.NavBar: <win-nav-bar>
* WinJS.UI.NavBarContainer: <win-nav-bar-container>
* WinJS.UI.NavBarCommand: <win-nav-bar-command>
* WinJS.UI.Rating: <win-rating>
* WinJS.UI.SearchBox: <win-searchbox>
* WinJS.UI.SemanticZoom: <win-semantic-zoom>
* WinJS.UI.TimePicker: <win-time-picker>
* WinJS.UI.ToggleSwitch: <win-toggle-switch>
* WinJS.UI.Tooltip: <win-tooltip>
  * Note: expects a child <win-tooltip-content>

For all of the controls you can bind to all public properties and events and the camel cased property names conveniently map to attributes.

There's some things left to be done like WinJS.UI.SettingsFlyout and rounding out the support for two-way binding of things like ListView selection state.