sched: EAS: place sync=1 wakee on waker's domain

With sync = 1, if waker CPU is in big cluster and wakee task's
load is small enough to fit within little cluster CPU, at present
scheduler places the wakee always on one of little cluster CPUs.
This tends to hurt performance with lots of cache misses.

Try to place wakee task on the waker's CPU or its siblings.

Change-Id: I40d5eba872e016a9becd3b2ef6ce20099326087e
Signed-off-by: Joonwoo Park <joonwoop@codeaurora.org>