Combined SE-0366 (third review) and SE-0377 (second review): rename `take`/`taking` to `consume`/`consuming`

[xwu (Xiaodi Wu)]

@DevAndArtist

consume x + y // Parses as (consume x) + y

As a reader I would expect this to be consume (x + y) not (consume x) + y.

This has been already asked and answered:

SE-0366: Move Function + "Use After Move" Diagnostic

The revision states: move x + y // Parses as (move x) + y I wonder if there could be some more justification of this choice, as it behaves differently from try, etc. Might it be preferred to have move x + y parse as move (x + y), particularly since there would be issues using explicit parens due to ambiguity with hypothetical functions named move? Users could specify (move x) + y explicitly if that's what they want. Alternatively, is there room to make move have undefined precedence with s…