enable max retries logic for controller execution test

[juliangaal]

Keep in mind that the #261 PR will provide some testing the affected class (but I would need to adjust the tests to the changed behavior). source

Attemps to fix the controller execution test broken since #263

Steps taken to pass this condition:

• enable max_tries: max_tries_ = 1
• in first Iteration, the code reaches this condition, which is tested after the first waitForStatusUpdate() call in the test

else
{
  setState(NO_LOCAL_CMD); // useful for server feedback
  // we keep on moving if we have retries left or if the user has granted us some patience.
  moving_ = max_retries_ || !patience_.isZero();
}

• in second interation, code reaches crucial part: after calling second waitForStatusUpdate(), the state is now finally MAX_RETRIES

if (max_retries_ > 0 && ++retries > max_retries_)
{
  setState(MAX_RETRIES);
  moving_ = false;
}

Cheers

[dorezyuk]

@juliangaal cool thanks for the fix