sched: fair: Stop running idle_balance on active migration kick

Newly_idle/idle cpu does load balance for each domain level,
if the idle cpu kicks active migration on busiest cpu at one level,
it still continues to do load balance at higher level. This behavior may
cause more packing on the current load balancing cpu, as it can pull tasks
from next domain level busiest cpu, as well as active migration would
moves task from busiest cpu.

Currently, it stops load balance if it directly pulled tasks
(pulled_task > 0), extend it to active migration as well.

Change-Id: I1dfa82590a382a06467827d05581ceaac84d5e1f
Signed-off-by: Lingutla Chandrasekhar <clingutla@codeaurora.org>