Change axis default on a number of functions in uproot-raw codegen

[ponyisi]

We make many awkward functions available when writing cuts and expressions for uproot. A lot of these default to operating on the entire array at once (axis=0) in ways that make no sense for an event-by-event cut mask. In general this default causes a lot of errors. We will override those defaults here (we believe the defaults are so incorrect that nobody with correct code will be affected by this). The axis can still be overridden if people want. The list of functions with changed defaults will be given in the frontend documentation.

[gordonwatts]

I really don't like this. I get why you are doing this. But this is magic and now behaves differently than regular code. So what users learn will break here.

btw - if axis argument is specified twice will this work?

[ponyisi]

It will work if the user specifies axis again. (It doesn't work if a user specifies it as a positional argument instead of a keyword one but this is a very rare pattern.)

I understand why this would make one uncomfortable but the fact is that essentially every new user I've seen work with the uproot-raw transformer makes the error of not specifying axis=1 in a relevant place and unless they're quite competent with awkward they don't figure it out on their own. When awkward specifies axis=0 as a default this is never the behavior you want here (unless you can come up with a circumstance where we want queries to correlate across events ...). The biggest likelihood of causing problems, I would guess, is actually that some inexperienced users come up with some cut expression that works in uproot-raw and not when they run awkward locally.

The equivalent RDataFrame expressions don't need this kind of silliness to work correctly...

[ponyisi]

I suppose we could make it an option in the uproot-raw request (though I would still want the default to be the override).