DISC/DES: EA should have transpose, T, ravel mirroring ndarray/Index/Series
As long as EA is 1D only these are all no-ops, so implementation is trivial.  It would save a bunch of special-casing and checking for exactly what type of object we have at different stages.

The cost is API clutter.

I'm of the opinion that EA should be as close as possible to a drop-in replacement for ndarray, (both for our purposes and so it can be useful in the ecosystem), so we _should_ implement these properties/methods.

Last I heard @TomAugspurger came down on the less-clutter side of this question.  Anyone else have an opinion?