Fix for: ENYO-56

# Issue

When using the delegate support for forward events from declarative child-components to an owner handler, directly, it is being lost from repeater children. This happens because children of repeater children are scoped to be owned by the repeater child for scoping related issues for a repeated child. This does, however, keep the expected behavior of delegated events from working.

# Fix

We can clearly identify when those cases exist and we can attempt to forward them to the owner of the repeater child (expected behavior) when possible.
I think we need to return true here regardless because we're short-circuiting the usual event bubbling chain. Otherwise, it's possible (albeit remote) for an upstream handler to be called twice. See the attached App.js in JIRA for an example.