FIX: invoking a widget with data-part overrides within a data-part

invoking a widget with data-part overrides within a data-part does not work.

example:
<div data-bind="widget: outer">
 <div data-part="outer-widget-part">
  <div data-bind="widget: inner">
   <div data-part="inner-widget-part">
     this will not take effect
   </div>
  </div>
 </div>
</div>

reason: the outer widget consumes the data-part of the inner widget.

solution: ignore data-parts within widget bindings
Fixed issue which caused optimizer to fail to launch RequireJS when run from command line
exposed parseMarkupCore for overriding
refactored "parseMarkup" logic

Renamed "parseMarkup" to "processMarkup", since it did more than just
parse.
Renamed "parseMarkupCore" to "parseMarkup" since that really did just
parse.
Exposed "parseMarkup" as public as well to make it overridable.
Updated the unit tests to reflect this and test the new public
"parseMarkup" overriding logic
fix for processMarkup call to parseMarkup

Somehow this was working in the unit tests and not in the index.html
page calls. This is the correct approach though.
added ability to remap default widget folder

by exposing new methods "mapKindToModuleId" and "mapKindToView" on the
widget module, users can now remap widget folders without losing the
explicit module mappings from methods like mapKind()
adding template widget.js files

Forgot the template versions of the same file
Major cleanup on new history module.
A little more reorg.
Some work prepping new router for actual code.
Adding some helpers to system and refactoring where appropriate.
Some more prep to implement the real router.
Tweaking the new router api.
Tons of work on the new router.
Adding some more missing basics to the new router.
A little closer to a functional router.
Adding  nav model capability and cleaning up the API of the router.
Some more router cleanup and bug fixes.
Robust mapping of unknown routes.
Better deep link support in new router.