`ark-cli`: Shell compatibility

Example with reading properties:
```
$ ark-cli file read . properties 22-207093268

{"ai":"true","desc":null,"favorites":"true","title":"duck"}
```

Expected result:
```
{
"ai": "true",
"desc": null,
"favorites": "true",
"title": "duck"
}
```

Actual result:
```
$ ark-cli file read . properties 22-207093268 | jq
parse error: Invalid numeric literal at line 1, column 8
```

In this particular example, the problem is only message `"Loading app id at /home/kirill/.ark..."`. This could be solved by introducing verbosity levels. However, we should also ensure that other commands provide composable outputs.

- [ ] **Write information messages into `stderr`, so they don't get into pipe (`|`)**
- [ ] **Implement verbosity control, e.g. `-v` for more details or `-q` for only result**

Start with the ark-cli file-read command shown in the issue and trace how its informational message is written when output is piped to jq. The work is complete when informational output no longer contaminates composable command results and verbosity controls support detailed, quiet, or result-only output across the relevant commands.

Written by the indexing model from the issue text.