Command coordinates precision vs. ArduPilot log

I'm not sure where to file this issue.

MissionPlanner stores waypoints/commands with coordinates in the following way (example):

```
7 0 3 16 0.000000 0.000000 0.000000 0.000000 51.077282 10.988579 20.000000 1
```

ArduPilot later creates logfiles with the following content:

```
CMD, 42187994, 9, 7, 16, 0, 0, 0, 0, 51.07728, 10.98858, 20
```

As you can see, the **precision differs** by one decimal place. One could argue if this is a bug or not but it for sure confused me while doing a custom analysis. The additional MP decimal suggests more than ArduPilot can handle. Would you consider removing it?

No file, test, or entry point is named. Trace where Mission Planner formats and stores command coordinates, compare that output with the ArduPilot CMD log precision, and confirm that the displayed or stored precision matches the supported log precision without changing coordinate values.

Written by the indexing model from the issue text.