Re-make .identifier as .name on ops

[masak]

Why do we store the identifier, the way to get at the routine that we're actually interested in? I dunno, historical reasons, perhaps... Anyway, it should be the routine itself.

It's also interesting to think how this affects the qtype property in unquotes, and the identifier property in object terms, both mentioned in #359. Maybe they should also be referring directly to their thing?

[masak]

...no. Closing.

The correct hook to hang an operator on is as a symbol lookup in a scope. Because in the general case, we don't have the actual routine, because the operator was declared as e.g. a parameter.

Maybe in the other two cases there's less dynamism, but I'm not so sure about that either.

[masak]

Hm, but it should actually be a name, not an identifier, because in

test.assert foo(), 42;

test.assert is a prefix operator, not a term. Hmmmmmmmm.

[masak]

Nope. See #417 (comment).