Whether to reduce or not, elaborated vs. non-elaborated

Usually, the check for whether or not to reduce an expression is dependent on the `reduce` argument to the CompileHelper members. However, the flag doesn't always account for whether the functions are being called in elaborated mode or non-elaborated mode context. There are cases where the functions explicitly force a reduction by passing `true` downstream disregarding the input `reduce` flag. I have tried to fix this issue in currently open/blocked PR #3651, but ran into other unexpected differences.

Question: Is wrapping the reduction call sites with both both `m_elabMode` and `reduce` the right solution to disable reduction in non-elaborated mode? If not, what more need to happen?

P.S. I pointed out this issue in the recently merged PR #3758 as well but since it didn't catch your eye, reporting it as an actual issue since this needs to be accounted for in lot more other places than just this specific change.

Start by reading the CompileHelper members and the reduction call sites discussed in PR #3651, then compare them with the elaborated and non-elaborated behavior noted in PR #3758. Determine the intended interaction between m_elabMode and reduce, and define what consistent reduction behavior should look like before changing the affected locations.

Written by the indexing model from the issue text.