fix #897 test.aria.utils.Html test fixed in IE7

Close #563. Close #569. Close #912.
fix #926 - blur not triggered in multiselect for IE

a click in a text input does not trigger the
blur event on the previously selected multiselect input, so
that the activeElement does not change properly
fix #833 Widgets cursor position is incorrect
feat #102 add `timeout` for `RequestMgr.sendJsonRequest`/`submitJsonRequest`

It's been always possible to pass a `timeout` to the calls of
    `aria.core.IO.asyncRequest`
    `aria.core.IO.asyncFormSubmit`
but not to the calls of
    `aria.modules.RequestMgr.submitJsonRequest`
    `aria.modules.RequestMgr.sendJsonRequest`

The latter only had the `aria.core.IO.defaultTimeout` applied.

This commit makes it possible to pass `timeout` as the key of the request
parameter object (first parameter) of them.

Close #102. Close #913.
fix #929 Incorrect short weekdays in Thai language

Short weekdays names were not correct in the date resources for Thai language.
doc Update README
fix #641 Possibility to package page engine resources

This commit introduces the possibility to retrieve site configuration and page definitions from a bundle.
fix #934 Missing and duplicate tests in the suite
fix #858 bump dependencies

Sorted them alphabetically by the way. Minor code fixes done for new
versions of JSHint and Jade.

Close #916.
feat #935 Addition of resources for Estonian language

Close #935
doc Incorrect sample in bean definition for IOAsyncRequestCfg

headers property in aria.core.CfgBeans:IOAsyncRequestCfg had an incorrect sample.

Close #938
fix #939 Overlay behaviour when body is scrollable

Loading indicators associated to an element are supposed to be cover and be cenetered only in the visible portion of the element.
This worked correctly apart from the case in which the body of the document has scrollbars. In that case, the overlay was not constrained to the viewport.

This commit fixes the issue by always constraining the overley in the viewport.

Furthermore, two other issues have been tackled by this commit:

* loading indicators were not being refreshed on window resize
* The message displayed underneath the spinner could end up outside the element, or was simply mispositioned in early versions of IE.
fix #936 Cross icon is no longer displayed for input widgets
fix #933 mispositioned labels in TextArea in IE7

This commit fixes the display:inline-block bug in IE7 that is affecting the label position for the TextArea widget.
feat #921 aria:List widget refresh on datamodel change

Now when you use aria.utils.Json.add and aria.utils.Json.removeAt functions to add items to an aria:List widget (or to remove one), the list template is refreshed and it displays the new item.
doc Improve Aria.load method documentation

Close #943
Always register a binding to section processing

If section processing is not bound to any data model, a spinner overlay created using setProcessingIndicator on the SectionWrapper does not follow it as one of its parent is moved and not closed if the section is deleted. Thus if the user does not specify any binding the overlay remains at its initial place forever.

Binding it to a dummy container allows both of the shortcomings to be solved: spinner follows its parent section and is closed upon section removal.
fix #945 Button text alignment in IE7

This commit fixes a problem on IE7 where text inside buttons is not centered.
doc Properties wrongly considered static in APIDoc

The documentation of the code is generated from JSDoc comments, which are parsed with an external tool. It is possible to document let's say detached properties, and to explicitely set their names with a special tag in the JSDoc. However, the tool in question uses this name to determine if a property is attached to an instance, a prototype or is static.

Therefore I prefixed the last part of the names with the proper container name when applicable:

- "prototype" for prototype members
- "instance" for instance members
- nothing for the others, which will be detected as statics (excepts for Aria members which are all considered to be in its prototype)

I took the opportunity to improve the documentation of the Modifiers class, explaining that modifier methods are not actually directly accessible.

Closes #947
feat #914 MultiAutoComplete Widget with more changes

Close #915