add radio locator management features

[caver456]

See #576 for the back story. Basically, SARTopo LocatorGroups are deprecated, will be going away at some point, and, for the past several CTD versions, they no longer provide left bar objects per radio.

Radiolog has been sending locator update requests to CTD since the early days, and should continue to send those same requests since they are used by Shared Locations. But, this is the first time that radiolog will need to interact with CTD enough to merit use of sartopo_python. (So it would make sense to use sartopo_python for the existing-style locator update requests also.)

Tasks:

• [x] https://github.com/ncssar/sartopo_python/issues/46
  • [x] editFeature (already exists in sartopo_python repo)
  • [x] delete marker (already exists in sartopo_python repo)
  • [x] https://github.com/ncssar/sartopo_python/issues/47
  • [x] https://github.com/ncssar/sartopo_python/issues/48
  • [x] https://github.com/ncssar/sartopo_python/issues/49
  • [x] https://github.com/ncssar/sartopo_python/issues/50
• [x] connect to a CTD map
• [ ] read from connected map: maybe the Radios folder and some radio markers already exist?
• [ ] offer to automatically connect to latest map (and show name) at startup
• [x] sts link indicator light in options dialog
• [x] sts link indicator light in main GUI?
• [x] make a folder for all radio markers
• [ ] if changeCallsign is needed, defer sending of marker until changeCallsign accept, or change label of existing marker (or delete it and add a new one) on changeCallsign accept
• [x] if sts is not yet created, queue radio markers and maybe show a one-time warning; process the queue as soon as sts is created
• [ ] confirm smooth operation when CTD is killed after sts was opened
• [ ] confirm smooth operation when map is deleted after sts was opened
• [x] confirm smooth operation if existing radio marker is deleted, then sent again
• [x] confirm smooth operation if entire Radios folder is deleted, then a radio marker is sent again [folder is recreated with no name, but can be edited; subsequent markers do go into that folder]
• [x] add a marker for the first call from a given radio
• [x] move the marker for subsequent calls from the radio
• [x] update the call time (in the 'Comments' field) on every call
• [ ] change color to gray after a certain time?

[caver456]

Adding a task to update sartopo_python on pypi. The version on pypi right now doesn't let you specify whether you want to sync, or what the default timeout should be. We want to send all of these requests in the same fire-and-forget manner as the existing locator update requests, with timeout of 0.001 sec.

[caver456]

pausing work here for a while, to do prerequisite work on sartopo_python

[caver456]

First of several steps finished towards sartopo_python pypi update. See that linked issue above for details.

[caver456]

re-re-re-thinking - adding this issue back to the v4.0 roadmap, for a few specific reasons:

• this task is significantly different than other sartopo integrations, for at least a few reasons:
  • doesn't attempt to modify assignment features
  • probably doesn't interfere with actions that any other IC personnel would take, so there's no need to address the topic of coordination / collaboration
• it's still a major enough feature to merit a major version number bump