Handle republishing smart events

[lsmith]

Maybe rather than registerEvent, it should use publish, and see how much logic could be reused from ET._publish.

Problem is two-fold:

1. target.publish('foo', {...}); then target.publish('foo', {...}, null, ['subscribe'])
2. target.publish('foo', {...}, null, ['subscribe']); then target.publish('foo', {...}, null, ['subscribe']); again.

Maybe three-fold if republished with a different set of routes ('subscribe', 'unsubscribe', 'fire').