PCTLIBRARY-935: Adds mechanism to add new view handlers to the view fixture.

ViewFixture.addViewHandler does not allow existing handlers to be
overridden (an INVALID_PARAMETERS error is thrown if this is attempted).
(@ewant)
Merge pull request #480 from BladeRunnerJS/develop

Develop > Master for 0.6 release
renaming some test methods to better represent what they do

 On branch test-suite-cleanup-and-refactoring
Merge branch 'develop' into test-suite-cleanup-and-refactoring
using new version of emitr after IE8 proto fix
changing test stub files to look more like the real thing and changing tests to use some new NodeJS/NamespacedJS specific methods
Begun the work of memoizing all computationally expensive getter methods
within the model and the core plug-ins. Also improved the dashboard
loading test so it shows the time taken when only some of the files have
been modified.
Make patch handling a pure plug-in concern so that source modules can
better limit when recalculation needs to occur. The down side to this
decision  is that plug-in developers are more likely to forget to add
support for patches if there is no API reminder of the need to do this.
refactoring some tests that dont need to verify the class contents
fixing javadoc paths used in checkSdkStructure task
Merge pull request #476 from janhancic/develop-caplin-patches-viewfixture

PCTLIBRARY-935: Adds mechanism to add new view handlers to the view fixture
Adding coverage for ViewFixture.js which includes the addViewHandler enhancement from @janhancic #476
Adding additional functionality for adding viewhandlers to the ComponentFixture (and tests)
CC: @janhancic
throwing an exception if dots are used for nodejs require paths
moving test util plugin to a more sensible package
making i18n content plugin text/javascript so its included in the composite bundle (#502)
Start forcing static intializer blocks that read files to be executed
when the file access checker is installed, so this file access doesn't
need to be made part of the memoization scope.
Ignore file access checks on directories (these are probably caused by
the File.exists() method) as this is likely just the model doing a
directory check for a parent directory of a file we are interested in --
this change will make memoization bugs possible again, but is unlikely
to cause bugs in reality.
Converted the NamespacedJsSourceModule plug-in to use memoization.
Merge branch 'develop' into test-suite-cleanup-and-refactoring