#### systemd service hardening

Running `radicle-node` as systemd service using our service files, will now run the service with some hardening options enabled. This work includes some trivial sandboxing options in the provided service files and lead users to `systemd-analyze security`.

While being a trivial change and far from a secure service it is an improvement and may push downstream packagers and / or users to add even a bit of sandboxing.

### Path to Windows

We continued working on Windows support for Radicle and made some progress on the node implimentation. As `std::os::unix` is obviously not available on Windows, resort to the `winpipe` crate, which implements a very similar API for named pipes. We now use `winpipe` to implement the node's control socket on Windows.

#### Bootstrapping improvements

When you start a fresh node, it'll need to have at least one seed that it can bootstrap from. We do this by using `iris.radicle.xyz` and `rosa.radicle.xyz` as bootstrap nodes. With this release, a node can now connect to them when DNS is not available or a connection via Tor is desired.

### CLI

- All commands now use verbose printing of authors

- In case of a panic, a human-friendly message is printed

- `rad sync status` and `rad node status` now use a table style that is more narrow

#### Library

- Introduce a new module that provides an API for iterating over a COB's operations, given a range of commits

- Remove `anyhow` from `radicle-term` and `radicle-node`

- BREAKING: Removed `radicle::node::DEFAULT_SOCKET_NAME`, use `radicle::profile::Home::socket` instead

- BREAKING: Add a node event for canonical reference updates

- Fix panic when reading from SQLite database fails