Database cursor classes should report progress messages using the GeoEco logging channel, not GeoEco.DatabaseAccess

[jjr8]

Currently, the database cursor classes report INFO progress messages to the GeoEco.DatabaseAccess logging channel. The downside of using this channel is that when tool A invokes tool B internally, it cannot force these progress messages to be reported as DEBUG rather than INFO. If they were reported to the GeoEco channel instead, tool A could force them to be DEBUG. This is needed for situations where one tool calls another in a loop, as is done by the "Create Fishnets for Points" tool.

[jjr8]

Fixed in [126], which will eventually be released in MGET 0.4a1.