Fix constrained narrow/pipe tuple expression input inference
Previously constraints were not stripped when inferring function inputs for tuple expressions like the following:
// previously errored due to data being inferred as `number.moreThan<0>`
// now correctly inferred as number
const t = type(["number>0", "=>", data => data + 1])