fix: do not calculate new path in creep.moveTo when creep is fatigued, visualizePathStyle is set, and valid memorized path exists

[Richard-Krug]

This fixes issue #130

Problem:
Usually, creep.moveTo returns C.ERR_TIRED early when the creep is fatigued. However, when visualizePathStyle is set, this does not happen because the path still needs to be visualized. If a valid path is memorized, it is used for the visualization and then for moveByPath. If moveByPath succeeds (C.OK), creep.moveTo returns before a new path is calculated. If the creep is fatigued, however, moveByPath returns C.ERR_TIRED and a new path is calculated unnecessarily which wastes a lot of CPU.

Solution:
Add C.ERR_TIRED as a reason to return after moveByPath because the memorized path is valid and the creep is just fatigued in this case.