Add custom data types for angles and factors/percentages

Instead of using `f64` for all types of numbers, there are some with special significance.

- Angles can be represented by degrees or radians. Our data type should encode one unambiguous value, enforcing any nodes that want to construct or read an angle to do so with an explicit choice of degrees or radians. This should replace the Transform node's rotation and X-skew/Y-skew angles, avoiding the confusion that the inputs given in the node graph aren't the user-friendly degrees set in the Properties panel. (See [#2431](https://github.com/GraphiteEditor/Graphite/pull/2431))
- Percentages can be represented out of 100 (percent) or 1 (factor). This distinctly represents not a quantity but a portion out of a whole, so it needs its own type. This avoids the confusion and mess caused by our current inconsistent usage of percentages and factors in various places, with uncertainty about whether those values are out of 1 or 100 when fed by the node graph. We can ensure number input widgets in range mode display the factor or percent on a per-case basis for whichever is designed to be the more logical approach, or do what Blender does and offer an app preference to display all such quantities as out of 1.00 or out of 100%.

Comienza rastreando los valores de rotación y X-skew/Y-skew del nodo Transform y, a continuación, sigue las entradas numéricas del grafo de nodos descritas en el issue. Identifica los usos incoherentes de porcentajes y factores y define el alcance afectado; el trabajo estará terminado cuando los ángulos y las proporciones utilicen representaciones explícitas y sin ambigüedades de forma coherente.

Escrito por el modelo de indexación a partir del texto del issue.