Find Nearest Features tool should not require that the input features be in a projected coordinate system

[jjr8]

Currently, Find Nearest Features requires that either the points or the near features or both be in a projected coordinate system. I did this because I assumed that the tool would only be used when someone needed to know the an accurate linear distance to the nearest feature. But at least one MGET user simply wanted copy fields from the nearest feature, without caring about the distance to it. I should change the tool to allow this, but issue a warning if neither the points nor the near features are in a projected coordinate system.

[jjr8]

Released in MGET 0.8a39, possibly an earlier release.