Description

Output dimensional order was always ..., Y, X where ... is all other dimensions. This would cause an error when adding bounds as the input dimensional ordering was used in this process.

This PR fixes the issue by correctly transposing the output data to the same ordering as the input data.

• Closes [Bug]: Regrid2 breaks in _preserve_bounds because _regrid incorrectly transposes output_data shape, which doesn't align with original dim order used by bounds #625

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

If applicable:

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass with my changes (locally and CI/CD build)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have noted that this is a breaking change for a major release (fix or feature that would cause existing functionality to not work as expected)