target state not reached is now an error, not a warning

When max_tries is 1, not reaching the target state means that we will
give up on this component. So this error message needs to be an ERROR.
When max_tries is not 1, we'll retry, so it is only a WARNING (error
occured but app can compensate)
refine error handling for reaching target state

Now it will always produce an ERROR in the log when the last try fails.
In the case where no max_tries were configured, it will immediately
produce an ERROR. If a component fails to reach a target state and
there are still tries left, then it will produce a WARNING.