fix #1147 set lower timeout for test cases

This commit changes default test timeout from 60s to 20s (30s on IE7) to
give faster feedback to the developer.

Majority of our tests can run <10s, only a few tests require explicitly
setting higher timeouts for some browsers (most notably IE7 and
PhantomJS).
Remove postData from IOAsyncRequestCfg

Use `data` instead of `postData`.

Close #1057.
Remove aria.core.IO.useXHRHeader/defaultXHRHeader

Use `headers` and `postHeaders` instead.

Close #1057.
Remove IOAsyncRequestCfg:postHeader and related aria.core.IO options

Use `headers` in cfg bean and `headers`/`postHeaders` in aria.core.IO
instead.

Close #1057.
feat #984 noder-js: at-noder-converter transformation for some files
feat #984 noder-js: integration of noder-js
feat #984 noder-js: include bootstrap build in npm package

As the migration to noder-js temporarily adds an extra build step
to convert all files to CommonJS (with at-noder-converter), this
commit makes sure all converted files are individually present in
the npm package (in the build/target/bootstrap directory).
feat #984 noder-js: fixing an issue in case the DownloadMgr is not usable
feat #984 noder-js: fixing a packaging issue
feat #984 noder-js: loader plugin for resources providers

This commit adds a loader plugin for resources providers.
The plugin will simplify the migration to the new syntax.
feat #984 noder-js: cleaning of aria.core.JsonValidator

Removal of commented code for the addition of `aria.core.BaseTypes` as a dependency.
That base bean definition is alreay added in the bootstrap.
feat #984 noder-js: Dynamic dependencies restoration

Classes `aria.utils.History` and `aria.templates.Template` had dynamic dependencies that had been turned into static ones.
This commit creates a loader plugin for `aria.utils.History` and make the contextual menu class asynchronous for the `aria.templates.Template` class.
feat #984 noder-js: switching to noder-js 1.4.0
feat #984 noder-js: migration to at-noder-converter 1.0.1
feat #984 noder-js: fixing issue when using Aria Templates in node.js

It is now possible again to use Aria Templates from node.js with:
 require("ariatemplates");
 Aria.load(/* ... */);
 // ...
fix #1152 aria.utils.css.Transitions CSS rules lost when using @aria widgets

Close #1153
feat #1132 Add env. parameter for escapeforhtml

- added templateSettings in EnvironmentSettings
- added hasEscapeHtmlByDefault and setEscapeHtmlByDefault to Environment
- modified Statements.js to check this parameter
- added tests
feat #1132 Add test for env. parameter for escapeforhtml

Made a few changes to the feature implementation, one for code consistency and one for fixing a discrepancy in identifiers use.

The new use case has been tested:

- a template gets compiled with the parameter turned off
- a classical use case is run and checked regarding that
- the parameter is reverted

This required to have two tests, to be able to have two different template compilations. Therefore a bit of refactoring has been done too.

Close #1132
Close #1133
Close #1154
fix #1155 Add jsdoc tags when needed

After the migration of the new syntax, some previously inferred documentation properties need to be explicitly declared.
The required declaration have been added to the classe that have already been migrated to the new syntax.
feat #1156 Testing the packaged version instead of the unpackaged one.

close #1156