libscope captures events written to the console more than once about appscope HOT 1 CLOSED

The command echo is a shell builtin. With changes related to console, ref issue #32, we no longer see the duplicates.
When the built in echo is used we emit one event for the console only:
{"type":"evt","body":{"sourcetype":"console","id":"ubuntu-sh-/home/donn/scope/utils/dupcon.sh","_time":1611784048.773,"source":"stdout","host":"ubuntu","proc":"sh","cmd":"/bin/sh /home/donn/scope/utils/dupcon.sh","pid":235998,"_channel":"251529653813764","data":"foo 1\n"}}

We see a new process, sh, started for each echo command in the event stream. One and only one console event.

When /usr/bin/echo is used in place of the built in echo we see 1 event for each echo'd line; "foo 1", "foo 2", et. al.
We also see a console event for the new line; "\n" for every /usr/bin/echo. This is due to how glibc handles the new line.
There is a separate issue defined for combining console data such that we don't get the separate event for new line. Soon.

{"type":"evt","body":{"sourcetype":"console","id":"ubuntu-echo-/usr/bin/echo foo 1","_time":1611783662.906,"source":"stdout","host":"ubuntu","proc":"echo","cmd":"/usr/bin/echo foo 1","pid":235324,"_channel":"250529492523466","data":"foo 1"}}
{"type":"evt","body":{"sourcetype":"console","id":"ubuntu-echo-/usr/bin/echo foo 1","_time":1611783662.907,"source":"stdout","host":"ubuntu","proc":"echo","cmd":"/usr/bin/echo foo 1","pid":235324,"_channel":"250529492523466","data":"\n"}}

from appscope.