add explicit flags to remove some booleans in the CE typechecker

[baronfel]

This is a slight cheese-move away from primitive obsession.

Tinkering in the CE typechecking I kept getting mixed up around what the two boolean flags that tryTrans takes meant. So I pulled them out into named values and adjusted callsites for clarity.

Further documentation on the types could go into why specific flags are chosen.

[TIHan]

I think this change is good as I don't like boolean flags on functions, especially when there are a lot of them.

Would a change like this set precedent for similar changes in the future?

[baronfel]

I would love to make similar changes in the future, I just specifically scoped this one small so that I wouldn't cause as much churn and/or make the review harder than necessary. A little bit of the Boy Scout rule applied to the codebase :)

[TIHan]

The scope of it is fine, I'm just curious if that is the route we want to take from here on out.

[cartermp]

I would love it if we took a route like this to eliminate the magic bool flags. Every time I see a naked true and false my brain turns off, and that's including the code I wrote that does the same.