Minor fixes and test for glitchy flash behaviour.

Bug where flash was not moving a node from it's existing position,
but rather cloning / copying it.
Slight code cleanup, no change in logic
Add safety to nextSibling() in case parent is null
Add tests for checking the DOM Reference after doing inserts
Added toCollection() helper
Rearranged some code
Changed statics to inline vars for haxe3 switch changes

Was complaining that it expects a constant value
Deleted unnecessary comment
Slight code cleanup
Changed static vars to inline for Haxe3 "switch" changes
Changed import rules for Haxe3 (js.html instead of xirsys_stdjs)

Tried to keep it backwards compatible, but have not run unit tests...
Further attempt to fix Flash .append() weirdness
Updated EventManagement to use new Bean, Haxe3 typedefs

Seems to be working in Haxe3.  Have not unit-tested to see if Haxe2
compatibility was broken...
Changed hxml for haxe3 - use embed_js to make sure jquery is included
Update for haxe3 - get

In Haxe2 (and neko1.8) the macro parser for Xml ignored whitespace,
which was really convenient - it cleaned up our JS output significantly
and resulted in a smaller file size.

In Haxe3, the parser is much more accurate, and keeps all the whitespace.
I've modified our widget processor to emulate the old behaviour - because
I think it was preferable, and because it means our unit tests will still pass :)

Unit tests currently passing on JS, Neko, CPP.

Flash still failing because of weird issues moving elements that are already
part of the DOM...
Removed unnecessary imports

That aren't there in Haxe3, and weren't used anyway
Re-enabled widgetTests.  All passing.

Still more need to be written...
Function to create named property for an element using dtx-name
Call function on dtx-name attribute to create named property
Added unit tests for named elements