"regular" and bone animations do not play the same way

Actions on meshes react differently from bone (armature) animations when played.

This can be seen in 2 situations:
1) When (using the Play Action node followed by a Pause Action) an action is played.
- on a mesh action, the animation stops at the last frame of the action.
- on a an armature action, it reverts back to the first frame of the action.

2) When (using a custom node), an animation is played while specifying the playback speed and with a "repeat / no repeat" boolean value attached
- on an armature action, the "loop / no loop" value is honored (i.e. animation runs once, as expedted)
- on a mesh action, the "loop / no loop" boolean is ignored and the animation loops indefinitely. This happens even when it is hard-coded to stop in the haxe script as `animation.play(action, null, blendTime, speed, false)`; instead of `animation.play(action, null, blendTime, speed, loop);`.

The attached zip contains a .blend file and the custom node ("Play Action With Params") that allows specifying speed and "loop / no loop".

The file contains three animation sequences, triggered with the 1-3 keys.
- key "1" activates a mesh and a bone animation, using the regular PlayAction node
- key "2" activates the mesh action, using a custom node with "repeat" set to false
- key "3" activates the armature action, using a custom node with "repeat" set to false

[BoneAnimTest.zip](https://github.com/armory3d/armory/files/2604561/BoneAnimTest.zip)

*(drag & drop zipped .blend file here)*

Start by opening the attached BoneAnimTest.zip and reproducing the three sequences triggered by keys 1–3, comparing the regular Play Action node with the custom “Play Action With Params” node. Trace the mesh and armature animation entry points used by those nodes and the Haxe call shown in the issue; done means pause stops both action types at the same expected frame and the repeat/no-repeat setting is honored for both.

Written by the indexing model from the issue text.