output: drop processing messages

[tychoish]

While it's useful for debugging, the latency on operations is low
enough that if we don't get a response in a few seconds, we know that
there's a problem, and otherwise acknowledging the message isn't
particularly useful and just makes it harder to look at slack channels
where pool toy is used.

[okwme]

the only time that it takes a long time is actually when a new user arrives, which is also kind of a premier moment for good status feedback. there should actually be a way to make slack remove the status message after the result message is delivered but i never figured it out.

i'd be happy to remove this feedback functionality but would be good to track the ideal scenario somehow... maybe i'll make an issue just so that it isn't lost.

[okwme]

got it tracked now : )

[okwme]

oh noooo the autodeploy failed:

======CMD======
source ~/.zshrc
killall -9 slackbot
cd ~/slackbot && git pull && go build
source ~/slackbot/.env
~/slackbot/slackbot &> ~/slackbot.log  &!

======END======
out: [oh-my-zsh] Would you like to update? [Y/n] 
out: [oh-my-zsh] You can update manually by running `omz update`
err: not interactive and can't open terminal
err: not interactive and can't open terminal
err: From https://github.com/interchainberlin/slackbot
err:    1bbb7ac..7b4f5b1  master     -> origin/master
err:  * [new branch]      output-drop-progress-message -> origin/output-drop-progress-message
err: error: Your local changes to the following files would be overwritten by merge:
err: 	main.go
err: Please commit your changes or stash them before you merge.
err: Aborting
==============================================
✅ Successfully executed commands to all host.
==============================================