Kraken: BlueOS should automatically bind logs folder for any extension

Today, our docs instruct developers to use `/usr/blueos/extensions/` for _"storing logs, configuration files, and recorded data"_.

Specifically for logs, the best would be for these logs to be together with BlueOS logs, living at `/var/logs/blueos/extensions/`.

---

### Proposed changes:

1. Our docs should instruct the user to either (1) put their logs on `./logs`, or (2) set a bind to their internal logs folder to `/var/logs/blueos/extensions/`.

2. When not set by the user, Kraken should automatically add the bind, ending up with something like:

```json
{
...
"HostConfig": {
"Binds":[
"/var/logs/blueos/extensions/radcam-manager:/logs",
],
...
}
```

3. Ensure users can access and download all those logs, packed together with the current system logs.