feat #405 Error tool tip enhancement

Currently the logic for the error tool tip is contained within
aria.widgets.form.Input, the aim of this enhancement is to share code
efficiently between multiple types of widgets. Specifically for the
requirement of this feature, this means making the code for the error tool
tip not only available for "Input" type widgets, but also for "Action"
type widgets.

In addition, it must also be possible from within a template to have a new
widget property called errorTipPosition that will be used as the preferred
position for the error tool tip, if there is not enough available space
the framework will automatically calculate the best position for the error
tool tip. The property will be added for both "Input" type widgets and
also "Action" type widgets.

Close #405
fix #406 Scrollbars in splitter with nested templates

Extra scrollbars are displayed when templates are nested inside a splitter widget
doc #392 release notes templates

Add two release-notes templates to generate wiki and blog release notes pages
Close #392
fix #389 closeOnMouseClick of Dialogs with inputs

Forces the blur on the active input to store its value in the data model

Close #390
feat #414 CSS Animations

Add CSS animations, like slide, fade, pop and flip, using the utility aria.utils.css.Animations

Close #414
refactor Error responsibility in aria.jsunit.Test

aria.jsunit.Test holds a list of error messages raised by extending classes, however the logic to deal with these errors is inside aria.jsunit.Assert
This commit simply moves code from one class to the other, errors are now part of Test and Assert is left with methods used by developers and not the test runner.

Close #403
refactor tests

Fix some trivial errors in test cases

Close #410
fix #415 bulletproofing test cases

1. JSONP test didn't remove the IOFilters in case of failure.
2. MobileBrowserTest used to emulate numerous browsers and didn't restore
original values in aria.core.Browser.

Both of the problems above had influence on another tests when run in the
test suite without isolation.
fix #397 Left positioning of dragged element on IE8

It also includes :

  - Includes some drag test cases,
  - Fixes some webkit drag issues (a click trigger a mousemove with webkit)
  - Excludes a test case with PhantomJS (the viewport size is not well reported)

Close #416
fix #417 Drag utility fails after fix #397

The workaround introduced in #397 about the mouse move is now effective
only for webkit

Close #418