Consider splitting `LiteralNumericExpression` to `LiteralInt32Expression` + `LiteralFloatExpression`

[dead-claudia]

Engines heavily optimize integers, and they do currently parse 1 and 1.0 differently, taking 1.0 as a hint it's likely used as a floating point number and 1 as a hint it's likely used as a simple integer. Shouldn't the AST reflect this reality by giving them this helpful little tip?