`neofs-cli` default timeouts for `object put`/`object get`/etc are implicit

After https://github.com/nspcc-dev/neofs-node/pull/2135 a user can see the following (15-sec default timeout that did not exist before):

▶ neofs-cli object put -r s01.neofs.devenv:8080 -w services/chain/node-wallet.json --cid HrG4qXKc3fpvY1dBay4Jy4qtDgGbwEnDtikDUJTegZJi --file tmp/test.file 
Enter password > 
 276824064 / 10000000000 [=======>-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------]   2.77% 12s
rpc error: client failure: rpc error: code = DeadlineExceeded desc = context deadline exceeded

as a user, I would ask some questions:

1. "rpc error:"? Really? Network error? The node is down?
2. I have the progress bar, I see how it works and nothing is frozen, I control it and can send SIGINT if I want to. Why 15-sec timeout is forced? "Any object should be put in 15 seconds" is smth unnatural for a util (at least by default when a progress bar is active).
3. Why doesn't it work the same as wget/curl?

cc @532910, @MaxGelbakhiani, @aprasolova, @vvarg229

Start at the neofs-cli object put/get command entry points and compare their timeout behavior with the change introduced by PR #2135. Reproduce the shown object put command, determine the intended default behavior for progress-bar transfers, and inspect tests for the affected commands; done means the agreed timeout behavior is applied consistently and failures are reported appropriately.