[ENHANCEMENT] Consider renaming `eachblockstoredindex` to `blockeachstoredindex`

[mtfishman]

I think we should consider renaming eachblockstoredindex to blockeachstoredindex. I think that would be closer to the naming convention used in BlockArrays.jl, though I've been going back and forth about it.

[mtfishman]

@lkdvos @ogauthe curious to hear your thoughts on this, I've been going back and forth about this for a while.

[lkdvos]

more options is probably not what you want, but also possible: eachstoredblockindex

I see what you mean about block_ being the convention in BlockArrays.jl, but blockeachstoredindex does read a bit funny, while the other feel a bit more language-friendly

[mtfishman]

more options is probably not what you want, but also possible: eachstoredblockindex

I also considered that, but I didn't want the term blockindex to be conflated with the BlockArrays.BlockIndex type, which has a different meaning (i.e. it refers to an index within a block, not a block location itself).

I see what you mean about block_ being the convention in BlockArrays.jl, but blockeachstoredindex does read a bit funny, while the other feel a bit more language-friendly

Indeed, those are basically the main considerations. Anyway, I'll leave this open for now and we can think about it, I was hoping to complete low hanging breaking changes soon so that some of these choices don't get too ingrained but this one would be easy to change over if we wanted to.

[ogauthe]

I agree eachstoredblockindex recalls too much BlockIndex. I have a weak preference for the current eachblockstoredindex, I like that it starts with each such that I easily associated it with eachindex that plays a similar role. I find it harder to parse blockeachstoredindex. Overall I value convenience over strict naming convention when we have the freedom to name a new function.