Add Google Earth Target (closes #832)

[Gear-I]

Description

Closes #832

Adds a Target that collects Google Earth Pro's saved locations ("My Places") - placemarks, paths, polygons, and folders the user has saved or imported as KML data.

File location: verified directly against Google's own support documentation (support.google.com/earth/answer/166438, the page Google itself points users to for moving saved locations between computers) - myplaces.kml lives under %USERPROFILE%\AppData\LocalLow\Google\GoogleEarth. No existing Target in the repo covers Google Earth.

Why the wildcard (myplaces*.kml) instead of a fixed filename: in addition to myplaces.kml itself, testing showed Google Earth Pro also maintains a myplaces.backup.kml alongside it. The wildcard catches both without hardcoding a second filename. I could only partially verify from documentation alone.

Testing: installed Google Earth Pro, saved a real placemark to My Places, then ran kape.exe --tsource C: --tdest --target GoogleEarth --debug. The %user% wildcard correctly resolved to my real profile (and correctly skipped nonexistent Default/Public/defaultuser* profiles). Both myplaces.kml and myplaces.backup.kml were found and collected. They had an identical SHA-1 hash at test time, so KAPE's own dedup logic copied one and correctly skipped the other as a duplicate, visible in the CopyLog.csv

GUID generated fresh (9a4aea7c-e407-44e1-a783-c5038436ab48).

Checklist:

Please replace every instance of [ ] with [X] OR click on the checkboxes after you submit your PR

• I have generated a unique GUID for my Target(s)/Module(s)
• I have placed the Target(s)/Module(s) in an appropriate subfolder in Targets or Modules. If one doesn't exist, I have either added it to the Misc folder or created a relevant subfolder with justification
• I have set or updated the version of my Target(s)/Module(s)
• I have verified that KAPE parses the Target(s)/Module(s) successfully via kape.exe, using --tlist/--mlist and corrected any errors
• I have validated my Target(s)/Module(s) against test data and verified they are working as intended
• I have made an attempt to document the artifacts within the Target(s) or Module(s) I am submitting. If documentation doesn't exist, I have placed N/A underneath the Documentation header
• For Targets, I have consulted either the Target Guide, Target Template, Compound Target Guide, or Compound Target Template to ensure my Target(s) follow the same format
• For Modules, I have consulted either the Module Guide, Module Template, Compound Module Guide, or Compound Module Template to ensure my Module(s) follow the same format