Description:
When using the rotation component the order is YXZ as set by the component. When setting rotation programmatically the recommended approach is directly through Object3D.rotation (docs). It's implied that the following two behave the same:

// With three.js
el.object3D.rotation.set(
  THREE.MathUtils.degToRad(15),
  THREE.MathUtils.degToRad(30),
  THREE.MathUtils.degToRad(90)
);

// With .setAttribute (less recommended).
el.setAttribute('rotation', {x: 15, y: 30, z: 90});

However, this is only the case if the element has had a rotation component before. Otherwise the user would have to explicitly set or pass the order. For consistency this PR sets the euler order upon entity creation, avoiding the issue.
Example Glitch showing the inconsistency: https://glitch.com/edit/#!/mud-grateful-haze

Also noticed a small optimization opportunity. The rotation component sets the order separately, which actually invokes a setter that triggers a recalculation of the corresponding Object3D.quaternion. The Euler.set method actually allows the order to be passed as well, preventing this redundant calculation.

Changes proposed:

• Set rotation euler order upon entity creation
• Pass euler order into set method avoiding redundant calculations