Fix inverse of TransverseMercator

[juliohm]

Based on our investigations, the inverse of the TransverseMercator is not producing the same results of PROJ nor GeographicLib. This needs to be fixed in a second more careful round of review.

The issue shouldn't affect most use cases, but it does affect conversions between TransverseMercator (and UTM) and any other projected CRS since converting between two projected CRS requires calling the inverse of the source CRS.