Realize zero end-user overhead

[tmplt]

The whole point of RTIC Scope is to offer instant insight into firmware behavior if it's written in RTIC. Work remains to reach this point. Namely:

• Merge flashing configuration functionality with cargo-embed #94
• Use a RTICScope.toml instead of Cargo.toml metadata #92
• Deprecate cortex-m-rtic-trace #90
• Refactor: exploit cortex-m structs instead of rolling own? probe-rs/probe-rs#727
• Add iterator for instrumentation/extension packet arbitration and decoding itm#5
• Exporting app description during compliation for tracing purposes? rtic-rs/rfcs#51

This list is very likely to grow.

The end-user should only need to set some flags in the RTIC application declaration and potentially write some configuration in a checked-in file.

[tmplt]

A side-effect of rtic-rs/rfcs#51 would be the increased possibility of supporting more RTOSs other than just RTIC.