Use Experimental Outcome for error handling

[PatrickKa]

Description

After some evaluation, I decided that we should use the Outcome library for error handling, specifically standalone Experimental Outcome. Despite the name, it is very mature and preferred by the author. Most importantly, it can be used on embedded systems just by defining the BOOST_OUTCOME_SYSTEM_ERROR2_NOT_POSIX macro.

What "using Experimental Outcome" means is basically that we use experimental::status_result<T, E> as return types that either hold a valid value of type T or an error/status code of type E. Of course this also involves a bit more boilerplate, magic, and sugar but the end result will be nice.

Edit: Remove #237 from to-do list since it turned into its own epic.

To do

• Install standalone Experimental Outcome library STS1_COBC_Docker#21
• Get an example working
• Add error handling for EDU code #182
• Add error handling for UART code #183
• Add error handling for flash code #184
• Add error handling for FRAM code #185
• Add error handling for file system code #186