Add code input for number props

[benjamincloquet]

Experimenting on this issue #254

This PR aims to improve the regular number input (as seen for the position, rotation, scale props) by adding a toggle to allow the user to input simple code expressions.
In this context, a valid expression is an expression that can be resolved in isolation, eg. 2 + 2, Math.PI / 2, Math.sqrt(2) and so on. If a prop contains an identifier from an external variable (myVariable * 2), it then falls under the standard unhandled category.

Recommended review path:

• Code parsing mock and test
• Expression parsing implementation and addition to type-infer
• NumberOrExpressionInput component that wraps a NumberInput and a StringInput to allow switching between number and code inputs.
• NumberOrExpressionInput implementation with the code toggle button
• String utilities : just like we don't want undefined to end up as a string in the code when saving, we want to save actual expressions in the code (Math.PI instead of "Math.PI")
• Prop unwrapping to ensure the preview works correctly even with wrapped expressions

To be improved : there is no visible validation as of now, if an incorrect expression is saved, the prop value is silently replaced with undefined

[vercel]

@benjamincloquet is attempting to deploy a commit to the Triplex Team on Vercel.

A member of the Team first needs to authorize it.