feat: Interpret literal number types in the context of other parameters

[jordanrfrazier]

Description
Currently, literal numbers are interpreted as i64. This can have some annoying interactions when promoting types. For example, the get function:

get<K: key, V: any>(key: K, map: map<K, V>) -> V

requires the key and the map key to be type K: key, where key is any hashable type. However, if we try:

f1: get(4, Input.u64_to_s)

we interpret the 4 as an i64. Then, because we want the map key (a u64) to be the same type as the literal, we have to do the least upper bound of i64 and u64. This is an f64. Unfortunately, f64 is not hashable, and is thus not a key type class.

Expected Behavior
It would make sense if the literal could be interpreted in the context of the types around it -- i.e. it should be a u64.