fix: use lngCorrection naming consistently

[arpitagarwal1301]

Thank you for opening a Pull Request!

---

• An issue was opened before the change
• The title uses a semantic commit prefix
• This does not cause breaking changes to Java or Kotlin integrations
• Tests and linter pass
• Code coverage does not decrease
• No documentation update is necessary for this internal rename

Fixes #1382 🦕

Summary

• rename the local lonCorrection identifier to lngCorrection
• use the longitude abbreviation consistently in PolyUtil.distanceToLine
• leave all calculations and runtime behavior unchanged

Testing

• ./gradlew :library:testDebugUnitTest --tests com.google.maps.android.PolyUtilTest
• ./gradlew :library:build :library:lintDebug --stacktrace

AI disclosure

This behavior-neutral naming correction was prepared and independently reviewed with AI assistance.