Trace Buffer and other updates

[jreineckearm]

Fixes

• Contributes to [Feature Request]: ETB/ETR/MTB trace capture support vscode-cmsis-debugger#1069 and other open discussions

Changes

• Trace Formatter enablement rules: Simple rule to always enable the formatter and accept the overhead. Decided against adding to *.ctrace-run.yml file to preserve separation of concerns (trace source setup vs trace communication setup). Also, this would go much farther than just the decoder meaning more complication on debug sequence side. Rather consider adding a command line option for ctrace to override the automatism.
• Trace Buffer Workflow: Always delete files before new buffer capture. Alternative would be to use BufferStreamOut debug access function with append or overwrite mode to control file handling from buffer read sequence. But this would come at the cost of predictability from a capture run from a user point of view (is the history removed or not?).
• Fixed help text for ctrace CLI args --csv and --ctf (default changed to nothing gets generated if not specified).
• Added ctrace CLI arg -c, --channel to specify which <channel> raw files to decode. Alternative would have been to add a list of selected trace sinks to *.ctrace-run.yml which would mean mixing of concerns (trace source setup vs trace communication setup). The ctrace caller is responsible for filtering by <channel>, in the IDE case the CMSIS Debugger which has easy access to *.cbuild-run.yml.

Checklist

• 🤖 This change is covered by unit tests (if applicable).
• 🤹 Manual testing has been performed (if necessary).
• 🛡️ Security impacts have been considered (if relevant).
• 📖 Documentation updates are complete (if required).
• 🧠 Third-party dependencies and TPIP updated (if required).