Optimize the snap to route node on Digitized and Connectivity changed commands

[runeanielsen]

The following code should only snap if they're further away than a configured tolerance. This is needed because it is a very heavy operation to modify the geometry in the database, resulting in a 10x performance decrease.

The places that need to be fixed are marked below.

open-ftth-gdb-integrator/src/OpenFTTH.GDBIntegrator.Integrator/Notifications/RouteSegmentConnectivityChanged.cs

Lines 91 to 94 in 6d9d526

	var lineString = request.After.GetLineString();
	lineString.Coordinates[0] = new Coordinate(startNode.GetPoint().Coordinate);
	request.After.Coord = lineString.AsBinary();
	await _geoDatabase.UpdateRouteSegment(request.After);

open-ftth-gdb-integrator/src/OpenFTTH.GDBIntegrator.Integrator/Notifications/RouteSegmentConnectivityChanged.cs

Lines 105 to 108 in 6d9d526

	var lineString = request.After.GetLineString();
	lineString.Coordinates[lineString.Coordinates.Count() - 1] = new Coordinate(endNode.GetPoint().Coordinate);
	request.After.Coord = lineString.AsBinary();
	await _geoDatabase.UpdateRouteSegment(request.After);

open-ftth-gdb-integrator/src/OpenFTTH.GDBIntegrator.Integrator/Notifications/NewRouteSegmentDigitized.cs

Lines 88 to 91 in 6d9d526

	var lineString = routeSegment.GetLineString();
	lineString.Coordinates[0] = new Coordinate(startNode.GetPoint().Coordinate);
	routeSegment.Coord = lineString.AsBinary();
	await _geoDatabase.UpdateRouteSegment(routeSegment);

open-ftth-gdb-integrator/src/OpenFTTH.GDBIntegrator.Integrator/Notifications/NewRouteSegmentDigitized.cs

Lines 108 to 111 in 6d9d526

	var lineString = routeSegment.GetLineString();
	lineString.Coordinates[lineString.Coordinates.Count() - 1] = new Coordinate(endNode.GetPoint().Coordinate);
	routeSegment.Coord = lineString.AsBinary();
	await _geoDatabase.UpdateRouteSegment(routeSegment);