Use proper SQL identifier semantics for named call arguments

[kasiafi]

POC fix for #11120. Needs further discussion because it causes backwards incompatibility in argument resolution.

[findepi]

If we go this route, we should also change procedures and table procedures parameter declarations, to have parameters in uppercase.

cc @losipiuk @homar

[losipiuk]

If we go this route, we should also change procedures and table procedures parameter declarations, to have parameters in uppercase.

cc @losipiuk @homar

Yeah - exactly. I think it makes sense. @findepi do you see any realistic backward compatibility issues with this change? (i do not).

[findepi]

I think that would be fine from practical perspective.
cc @martint on the specwise aspect

@kasiafi if you want, i can take it from here.

Also, as a transition period, we could require procedures params to be uppercase, so that procedure implementors are forced to update, to keep queries from failing. And then unblock case sensitive params after couple releases.

[kasiafi]

@findepi feel free to take it.

[findepi]

-> #11163

[findepi]

Replaced by #11163