android/tester-ng: Make action calls non recurent
android/tester-ng: Make action calls non recurent

All action steps steps were called recurently if not interleaved with
callbacks steps in test case definition. This could block any potential
callback that was not expected to come, as mainloop was stuck. This could
raise potential stability issues and timeouts when working with file
descriptors and io channels handled in the main loop.

mapfau/bluez,mapfau/bluez,pkarasev3/bluez,pstglia/external-bluetooth-bluez,ComputeCycles/bluez,silent-snowman/bluez,mapfau/bluez,pkarasev3/bluez,mapfau/bluez,pstglia/external-bluetooth-bluez,silent-snowman/bluez,ComputeCycles/bluez,pstglia/external-bluetooth-bluez,pkarasev3/bluez,ComputeCycles/bluez,ComputeCycles/bluez,silent-snowman/bluez,pstglia/external-bluetooth-bluez,silent-snowman/bluez,pkarasev3/bluez