ecore: make efl_loop_future_scheduler_get shouldn't be exposed in the object function.

ecore: make efl_loop_future_scheduler_get shouldn't be exposed in the object function.

Function declared in a .eo are something that we want to allow people to inherit from
or use in a binding. I can't think of a situation where that would be the case for
this function and it solves at the same time problem of needing a shared interface
for both loop and loop_user.