FlxTween.start() behavior

• Haxe version: 3.4.7
• Flixel version: 4.4.2
• OpenFL version: 8.3.0
• Lime version: 6.4.0
• Affected targets: Tested on CPP and Neko

Code snippet reproducing the issue:

package;

import flixel.util.FlxAxes;
import flixel.tweens.FlxTween;
import flixel.text.FlxText;
import flixel.FlxState;

class PlayState extends FlxState
{
    override public function create():Void
    {
        var textRestart = new FlxText(0, 0, 0, "RESTART", 32);
        textRestart.screenCenter(FlxAxes.X);
        add(textRestart);

        var textStartCanceled = new FlxText(0, 72, 0, "START CANCELED", 32);
        textStartCanceled.screenCenter(FlxAxes.X);
        add(textStartCanceled);

        var tweenRestart = FlxTween.linearMotion(
            textRestart,
            textRestart.x,
            textRestart.y,
            textRestart.x + 50,
            textRestart.y,
            true);
        tweenRestart.onComplete = function(tween):Void
        {
            tween.start();
        };

        var tweenStartCanceled = FlxTween.linearMotion(
            textStartCanceled,
            textStartCanceled.x,
            textStartCanceled.y,
            textStartCanceled.x + 50,
            textStartCanceled.y,
            true);
        tweenStartCanceled.cancel();
        tweenStartCanceled.start();
    }
}

Observed behavior:

• Calling the start() method on a completed FlxTween doesn't restart the tween.
• Calling the start() method on a canceled FlxTween dowsn't start the tween.

Expected behavior:
Calling the start() method should always restart the tween from the beginning.

Start by reproducing the behavior with the Haxe snippet in the issue, then inspect the implementation of FlxTween.start() and its completed and canceled states. Done means calling start() restarts a completed tween and begins a canceled tween from the beginning.