Coverage for binary tests

[LesnyRumcajs]

Issue summary

Coverage reports are missing runs where the forest binary is executed directly, e.g. cli tests. Some attempts were made with adding --follow-exec to tarpaulin (perhaps the executed binary was not the instrumented one) or creating explicitly an instrumented binary (which was severely timing out, >20mins).

Task summary

• [ ] Investigate how we can make binary tests with coverage check (most likely it should be one binary for most cases, except where some fancy features are used)
• [ ] Implement the change

Acceptance Criteria

• [ ] main is at least partially covered
• [ ] coverage step does not take significantly more time than before

Other information and links

https://github.com/assert-rs/assert_cmd/issues/57 https://docs.rs/escargot/latest/escargot/ https://github.com/xd009642/tarpaulin/issues/105

An attempt at building instrumented binary once for all tests

lazy_static!(
    static ref FOREST_BINARY: CargoRun = {
    escargot::CargoBuild::new()
        .bin("forest")
        .current_release()
        .current_target()
        .run()
        .unwrap()
    };
);

// then use with: let cmd = Command::new(FOREST_BINARY.path())

[lemmih]

This might be solvable once #1558 lands.

[lemmih]

cargo llvm-cov magically does the right thing. We have good coverage and it doesn't significantly impact testing time.