[Feature Request]: Expand .dbgconf content to key-value pairs under `device-settings:`

[jreineckearm]

Description

#604 introduced the new node device-settings: under debugger:. It's functionality relates to the dbgconf: node under the same parent.

See https://github.com/Open-CMSIS-Pack/cmsis-toolbox/blob/main/docs/pyOCD-Debugger.md#device-settings

Brief summary of rules

• *.csolution.yml + *.cbuild-run.yml : Both device-settings: and dbgconf: are allowed in both files. If both present, then dbgconf: is ignored.
• *.csolution.yml -> *.cbuild-run.yml conversion:
  • If *.csolution.yml contains device-settings:, then it's passed to *.csolution.yml as is. An also existing dbgconf: node is ignored and discarded.
  • If *.csolution.yml contains dbgconf: only, then
    • the content of the *.dbgconf file is parsed.
    • variable assignments are converted into key-value child nodes under device-settings in *.cbuild-run.yml.
    • it's OK to discard the (C-like) comments that can live in the file for Configuration Wizard annotations.
    • no dbgconf: node is written to *.cbuild-run.yml.

Potential caveats:

• Variable assignments can be numeric values and expressions. But the latter is probably the rarer case. TBC
• Variable assignments can be multi-line, but lines should be terminated by a semi-colon. I would not expect variable assignments to be interleaved with comments.

Note: Consuming debuggers already support dbgconf: in *.cbuild-run.yml for legacy reasons. Hence, not a blocker.

Is this request a Security Requirement?

• Yes

[brondani]

In debug-vars and debug-sequences execute the variable assignments and function calls are represented in the Debug Description language, just as they are in PDSC.
Parsing only dbgconf files while leaving debug-vars and debug-sequences unchanged seems asymmetric and inconsistent.
Also note that there is currently no Debug Description (C-Like) parser in csolution.

[jreineckearm]

The difference is that debug-vars and debug-sequences are fed into debug sequence engines which already exist and are in use. And those sequence expressions (especially in debug-sequences) won't map well to yml nodes.

We changed device-settings (was debug-vars-set in an earlier proposal) from a similar string to what it is now. It needs to be easier editable and addable by users on *.csolution.yml level.

Longer term, we would like to go away completely from dbgconf: in *.cbuild-run.yml to make it as self-contained as possible. But keep it in *.csolution.yml to gain from the Configuration Wizard annotation. Hence the conversion step.