Add support for Potensic Atom 3 #870

Specs: https://www.potensic.com/atom-3-specs.html

• 1/1.3-inch CMOS
• Quoted battery life 40 mins.

More details: #863

Analysis of the files:

• It uses global.json and a xxx.json file for the waypoint missions, same as Atom 2.
• The global.json is exactly the same.
• The xxx.json file is slightly different:

1. No ;[] POI suffix. Atom 2 mission files are [waypoints];[poi_list]; the Atom 3 file is a plain JSON array ending }] - no semicolon, no POI array at all, no trailing newline. The main change here.
2. No fileName key on waypoints. Atom 2 always writes one (point_<ts>.jpg, a thumbnail for the Eve UI); Atom 3 omits the key entirely. Thumbnails are aesthetic only, so not an issue we need to action.
3. Two enum values not previously documented: yawType: "TO_WAYPOINT" (with yaw: 0 throughout) and zoomType: "HAND". Atom 2 captures only ever showed DEFINE for both. Most likely these are mission settings the selected manually in Potensic Eve in the example provided by @zigulicd? Perhaps it means 'set yaw heading towards next waypoint' and 'manual zoom' and are probably still compatible with DEFINE as an option too?

Everything else matches the Atom 2 exactly.