Add method to transpose WCS axes when they are in the wrong order

In fixing the order of the dataset keywords I broke dataset inventory because the new order of the dataset keywords doesn’t match the incorrect L0 WCS ordering. To remedy both this and the fact that the WCS ordering has been wrong in the L1 data after going through the VISP pipeline, this PR checks to see if the WCS keys are transposed. If they are, it transposes them again to fix them.