Tracking issue: `no_std` support

[matprec]

Supporting no_std environments will require an extensive amount of modularity.

We cannot assume implementations of networking crates, timestamps etc are implemented or available on these targets, as they are very much non standard. This means to effectively support no_std environments, users should be able to provide an own implementation for network and timestamps.

Some targets have to time capabilities in form of a timestamps, so we should also support cycle counts, too.