Query/Shaper: consider adding names to variables we generate

In shaper code we generate a lot of variables (this is how we often communicate between parts of the shaper processing code). At the moment the variables are always unnamed - we let compiler figure out the names when it's all done to avoid bugs due to name clashes. As part of AOT work we could/should consider adding the names to make the code more readable