fix(compiler): Correct exhaustive check on record adt with when pattern

[spotandjake]

This pr corrects exhaustive checking when inlined records are mixed with when clauses, like in the example below:

enum T {
  A{ n: Number, },
  B{ n: Number, },
}
match (B{ n: 1 }) {
  A{ n } => void,
  B{ n: 0 } when false => void,
}

Previously, we were not providing a warning, which was due to a small bug in Conv, where we didn't propagate any Any pattern. This handles the edge case correctly, allowing a warning to show up. However, I think we may want to take a deeper look into pattern matching semantics eventually, as the Conv logic feels fragile in general.

Closes: #2311

[ospencer]

Let's change this to match on both the values as well as cstr_inlined, explicitly matching on the Some(_) and None cases.

In the Some case, for the constructor values, if the list is empty, we should fail. If the list contains more than one item, we should fail. We then need to handle all of the cases that are valid. Is it just Any? Feels like Or and Alias are valid here too.

[spotandjake]

Instead of just handling all the casees I refactored this a tiny bit so that it's more explicit what type a constructor is.