Major re re refactor, step #1, details below:

The base event wasn't going to work because the default event needed to act as
a base event, but it was trying to handle relaying to smart events and other
stuff. Also, for the sake of compatibility, I needed to support new Y.EventTarget({ default config }) and non-emitting events.

* @DEFAULT => @default
* event.subscribe(target, phase, args) => (target, args, phase)
* CustomEvent.proto now facadeless
* +CustomEvent.FacadeEvent for emitFacade events
* lots of crazy logic in publish and configure to fork at publish-time for
  basing events off CustomEvent or FacadeEvent (curse you emitFacade!)
* smart events now implemented by CustomEvent.Router class that acts as a
  published custom event, but tests and relays to a registered smart event or
  the default event. Smart event routers are created by _publish() as
  @subscribe, @unsubscribe, and @fire if an event is published with the new
  _smart_ param passed. _smart_ takes an array of any of ('subscribe',
  'unsubscribe', and 'fire') for which routers to register with. This way,
  the smart event logic only impacts performance if a smart event has been
  published on the target/class *for the specific action*.
* probably lots more, but my brain is fried by all the emitFacade hackery :(
* gained 2k in minified weight for all this (mostly the emitFacade forking) :(
test_y_dom.html is redundant (now test_dom.html)
Fix Subscription notify() with payload

Improper use of concat was resulting in the arguments object being passed
as the first param to callbacks when the subscription had a payload.
Update for changes in eventx core

* subscribe(target, args, phase)
* Remove default event overrides for Y
* Use Y.Object(Y.Event.DOM_EVENTS) for Y, Node, and NodeList events collections
  to share DOM events
* more, but no notable functionality changes
Update simple manual tests for new eventx core

CustomEvent by default doesn't fire with a facade now, so those subs looking
for e and e.get() needed to be updated.
Add Y.Global

Still pending support for broadcast, though. Not sure how I want to handle that
one. I'd like to meet with the YUI peeps and get a poll from the community
before changing the currently screwed up behavior.