feat #339 PhantomJS Robot implementation

Close #339.
feat #335 configurable number of PhantomJS instances in Attester

Makes it possible to increase (locally, per-user) no. of PhantomJS
instances in Attester to parallelize the execution of the test suite
when launched via 'npm run-script attester' (and 'npm test').

Type in the console e.g.
 npm config set ariatemplates:phantomjsInstances 4
to change the default to 4.

Set it to ~= your processor's noOfCores * noOfThreads * 2
for max performance. E.g. on quad-core dual-threaded processor,
set it to 4*2*2 = 16.

Keep in mind that each thread consumes ~= 30-50 MB of RAM.

This commit requires attester 1.0.2.

Close #335. Close #337.
feat #80 bindable width and height for containers

Adds possibility to bind width and height for some of container-based
widgets (Div, Dialog, Fieldset, TabPanel). The bound size is a subject to
min/max size constraints for all of those widgets.

This commit lifts the requirement for widgets to have width/height = -1
for min/max width/height to work. So this is backward-incompatible change
in some way, but the behavior of width & maxwidth etc. when provided
together was undefined earlier, so it should not have relied upon by anyone.

Apart from the bindable width/height tests, this commit brings also
a test case on static height constraints of the Dialog widget and their
behavior when the contents od the Dialog change due to a refresh.

Close #80. Close #347.
feat #292 Mobile Device Properties
feat #344 Duplicated or misplaced error strings
feat #276 custom image for Iconbutton
fix #274 Refresh section attributes

Close #354.
feat #352 Orientation change detection functionality for mobile devices added to AT
feat #348 Animation/Transition Event callbacks
fix #348 animation event in non-browser

Make sure that Delegate can be loaded even in non-browser environments like Rhino or nodejs where window/document are not defined
feat #349 maximizable dialog

Dialog can be now maximizable. If configured so, it will have a button to
maximize/unmaximize next to the close button. It also reacts to the change
of the data model property "maximized". That property takes precedence
over center, xpos, ypos, width, height changes.

When maximized, Dialog occupies the whole viewport and is not
movable/resizable. After unmaximizing, it returns to the original
position, size and other capabilities.

Close #349. Close #358.
fix #349 maxwidth/maxheight issues in Dialog

After delivering #349 via commit 29331b13d5724498ca8bb8a8566564499ed0bf36
a regresion was found during release testing: maxwidth/maxheight
constraints of the Dialog were calculated too big due to addition of the
shadow. That addition should be done only in maximized mode.

Moreover, the Dialog was not correctly resized in maximized mode when
it had maxWidth/maxHeight set. Now that properties are ignored in
maximized mode.

Close #359.
fix #276 icon button test case
1.3.5
fix #355 button widget not focusable

In IE8+ the Button widget is not focusable because of the onfocusin method
used as an hack in <IE8
Closes #357
fix #365 skin inherited by the Bridge

closes #368
fix #273 additional whitelisted attributes

autofocus, autocomplete, autocapitalize, autocorrect and spellcheck attributes are now in the whitelist.
closes #372
fix #369 - AT Debug Tools not working on IE7/8 after AT v1.2-4
pull request #370
doc Getting started with AT

closes #375
fix #373 setJsonPostData uses deprecated properties

Instead of using the deprecated `jsonData` now use the standard `data` property to encode data information from a request filter
Closes #374