Feature #727 | Replace latlong with maps_toolkit

[yakanet]

As mentioned in #727 , replace latlong dependency with maps_toolkit.

The change is minimal, but it might create some breaking changes with other libs based on flutter_map, as the package name for the LatLong class is not the same, and the class LatLong is now immutable.

In most of the cases just replace the package name with the following:

- import 'package:latlong/latlong.dart';
+ import 'package:maps_toolkit/maps_toolkit.dart';

[kengu]

@yakanet Could you fix the conflicts before we look into your proposed switch to maps_toolkit?

[maRci002]

This package seems good, just resolve conflicts. I kinda like this package LatLng's hashCode override version.
However there isn't nullsafe version of it yet.

[danilocubos]

#854 Fixes this problem.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[1075dn]

I would prefer switching to maps_toolkit as well.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[ibrierley]

Not sure if this is still necessary now, would like to hear if people think it is and why, as there were conflicts and maps_toolkit can be used standalone if I'm understanding it correctly ?

[JaffaKetchup]

Would agree. Not sure if this is necessary now the new version of 'latlong2' is being used?

[JaffaKetchup]

I'm going to close this as 'latlong2' is now being used, which already has some of the same extra features as 'maps_toolkit'. Besides, if those extra functions are needed, you can just require that library separately?

Thanks for your contribution!

[JaffaKetchup]

Ok, for now, I'm going to close this PR. I don't think it's necessary anymore, and might cause more problems than create benefits.
Thank you for your contribution, and feel free to submit more in the future should you feel the need to. Thanks!