accountId: determine automatically if possible, in case it is different for each host

[caver456]

accountId required for CTD 4214 is different than accountId for online. Is that still true for more recent CTD?

Where is accountId used in sartopo_phython:

• creating a new map - if incorrect accountId is used, the accountobject account_id entry in the CTD database will be NULL - not sure what that affects but it's probably not good
• printing - currently, printing is not done by sartopo_python, but it belongs here and will probably be brought in at some point. accountId is part of the POST request (/api/v1/acct//PDFLink) which doesn't work on CTD 4214 so can be sent to sartopo.com instead; if the CTD 4214 accountId is used in the sartopo.com print request, it probably won't work.

Anyway: it would be best to determine accountId automatically at runtime, rather than needing to hardcode it in the config file. If it is still different on different hosts, maybe the config file will have to have multiple accountId entries - one per host.

If it still does need to be different per host, then how would CTD determine the correct accountId needed to send a print request to sartopo.com?