chore: reveal inner tests log

It's already formatted in conformity with a usual cargo test.

Also, remove unused command-line arguments from picodata test command.

Success example:

    Running test/inner.rs (target/debug/deps/inner-372f328a84175650)

running 5 tests
test test_storage_state ... ok
test test_storage_log ... ok
test test_version ... ok
test test_traft_pool ... ok
test test_mailbox ... ok

test result: ok. 5 passed; 0 failed; finished in 0.56s

Failure example (artificial):

    Running test/inner.rs (target/debug/deps/inner-372f328a84175650)

running 6 tests
test test_storage_peers ... ok
test test_storage_state ... ok
test test_storage_log ... ok
test test_version ... FAILED

2022-05-26 12:45:08.090 [2431992] main/103/interactive C> Tarantool 2.8.3-0-g01023dbc2
2022-05-26 12:45:08.090 [2431992] main/103/interactive C> log level 5
2022-05-26 12:45:08.090 [2431992] main/103/interactive I> wal/engine cleanup is paused
2022-05-26 12:45:08.090 [2431992] main/103/interactive I> mapping 268435456 bytes for memtx tuple arena...
2022-05-26 12:45:08.090 [2431992] main/103/interactive I> Actual slab_alloc_factor calculated on the basis of desired slab_alloc_factor = 1.044274
2022-05-26 12:45:08.090 [2431992] main/103/interactive I> mapping 134217728 bytes for vinyl tuple arena...
2022-05-26 12:45:08.095 [2431992] main/103/interactive I> instance uuid 8f96389e-6a7d-4af8-a1e7-7e6e3d586f91
2022-05-26 12:45:08.095 [2431992] main/103/interactive I> tx_binary: stopped
2022-05-26 12:45:08.095 [2431992] main/103/interactive I> tx_binary: bound to 127.0.0.1:43095
2022-05-26 12:45:08.095 [2431992] main/103/interactive I> initializing an empty data directory
2022-05-26 12:45:08.120 [2431992] main/103/interactive I> assigned id 1 to replica 8f96389e-6a7d-4af8-a1e7-7e6e3d586f91
2022-05-26 12:45:08.120 [2431992] main/103/interactive I> cluster uuid 0ea2c203-1a3e-4ba6-9a66-262bca4147c5
2022-05-26 12:45:08.121 [2431992] snapshot/101/main I> saving snapshot `./00000000000000000000.snap.inprogress'
2022-05-26 12:45:08.124 [2431992] snapshot/101/main I> done
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> ready to accept requests
2022-05-26 12:45:08.124 [2431992] main/104/gc I> wal/engine cleanup is resumed
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> set 'log_level' configuration option to 5
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> set 'feedback_enabled' configuration option to false
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> set 'listen' configuration option to "127.0.0.1:0"
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> set 'replication' configuration option to []
2022-05-26 12:45:08.124 [2431992] main/103/interactive I> set 'log_format' configuration option to "plain"
2022-05-26 12:45:08.124 [2431992] main/105/checkpoint_daemon I> scheduled next checkpoint for Thu May 26 14:01:30 2022
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `"Tarantool"`,
 right: `"2.8.3-0-g01023dbc2"`', src/tarantool.rs:97:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5

test test_traft_pool ... ok
test test_mailbox ... ok

test result: FAILED. 5 passed; 1 failed; finished in 0.70s

thread 'main' panicked at 'assertion failed: status.success()', test/inner.rs:7:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: test failed, to rerun pass '--test inner'

Close #61 (closed)