Rename `Transpose` to `Permute` to Reflect Behaviour

Is your feature request related to a problem? Please describe.
The Transpose and Transposed transforms actually permute based on the axes given to them, they don't just swap dimensions 0 and 1 as the name implies. A transform created as such for 2D data mt.Transpose((0, 1)) will appear to be a no-op even though it appears the users is specifying to transpose axes 0 and 1, mt.Transpose((1, 0)) is needed to get the desired effect because the argument is actually specifying what the permutation should be.

Describe the solution you'd like
Rename classes to Permute and Permuted with new classes inheriting from them with deprecation warnings.

Describe alternatives you've considered
The transforms work just fine.

Additional context
I was momentarily confused by the name so I suspect others have been as well.

Start from the Transpose and Transposed transform classes and inspect their tests and references in the repository. Rename the primary classes to Permute and Permuted, retain deprecated compatibility classes with warnings, and update coverage so the existing permutation behavior and deprecation path are verified.