Correct geodetic scale denominator calculation

[fdiazcarsi]

This commit fixes a bug in the getGeodeticDenominator method within the Scale class.

Problem:
The calculation for minGeoX, which defines the starting X-coordinate of the horizontal line segment used for geodetic distance measurement, incorrectly used position.y instead of position.x. This resulted in the geodetic calculation being performed at an incorrect location on the map, leading to an inaccurate scale denominator.

Fix:
The minGeoX calculation has been corrected to use position.x - (geoWidth / 2.0), ensuring that the horizontal line segment is properly centered around the provided position's X-coordinate.

Impact:
This fix ensures that geodetic scale denominators are calculated accurately, improving the precision of map rendering and scale representation, especially for projections where geodetic corrections are critical.

[sbrunner]

Can you clear your pull request by doing an interactive rebase and removing all the extra commits?

[fdiazcarsi]

Hi! As requested, I've cleaned up the PR history using an interactive rebase. It should now contain only the relevant commit on top of the latest master. Ready for review again. Thanks!

[sbrunner]

@sebr72 does it look good to you?

[fdiazcarsi]

Yes, thank you.

[sebr72]

@sbrunner
I agree with the intent of the PR. But what really puzzles me is the fact that none of the tests failed with such change.

@fdiazcarsi
Thanks for spotting and fixing this.
But since this PR is intended to be deployed to 6 versions, I believe that this kind of change must be tested.

[sebr72]

As a general practice, we always add tests when making changes. But in this case in particular (as it appears to be a very old bug - and sometimes they are not), please create at least a Unit test if CI test is not required: Your decision