Refactor HyperlinkClickHandler to cleanup event binding

Move control of event bindings from SessionController to
HyperlinkClickHandler so bindings will be updated whenever modifier is
changed. This allows some simplification as HyperlinkClickHandler can
simply use the KeyboardHandler.Modifier.
Remove unnecessary duplicate click handler in the viewer plugin

The viewer was quite recently modified to use a session controller to
take advantage of the improved selection rendering system. This makes
the manual creation of the hyperlink click manager unnecessary.
Add tooltip support for hyperlink
Enable the hyperlink tooltip in the ODT viewer
Merge pull request #439 from peitschie/hyperlinkTooltip

Add tooltip support for hyperlink
Catch and log unhandled exceptions in async tests
Remove and ignore files created by tests
Add clarification comment on how the meta element behaves (and test)
Don't stop parsing an ODF unless the container state becomes invalid

An error is not necessarily fatal unless the handler sets the state to
invalid as a result of the missing data. In addition, when the state
is set to invalid, log the component that failed to load and (if
defined) the error that has occurred.
Handle documents with no office:settings element

Settings.xml and office:settings are both optional according to the
ODF specifications. WebODF must be able to handle loading and saving
files with or without this setting.
Ensure all ODF elements are recreated when setting a new root element
Merge pull request #466 from peitschie/optional-settings

Handle documents with no office:settings element
Noting agreed coding rules for types
Merge pull request #420 from kossebau/codingPolicy

Noting agreed coding rules for types
Remove wordpressplugin (for more concentration on the one for ViewerJS)
Merge pull request #478 from kossebau/removeWPPlugin

Remove wordpressplugin (for more concentration on the one for ViewerJS)
Add failing test showing crash with apply styles op
Use ranges when applying a style to better handle DOM changes

When first created, the text style applicator used to move nodes around
within the first while loop, often modifying the limiting range in ways
that were not expected.

In 5a86bdd, this behaviour was re-written to gather all the relevant
nodes and migrate them once all siblings in the container were checked.
With this change, it is now best to use the range once again, as this
avoids additional problems (see the modified test) with new children
being added within the range if new styling containers are inserted.
Merge pull request #444 from peitschie/apply-style-crash

Use ranges when applying a style to better handle DOM changes
Re-implement paragraph & document selection using step iterators

Changes in adjustSelectionByNode logic fixes extend-by-paragraph
problem (issue #335).