Feature/ Add test_prefix support under configured runner

[Edoardo-en]

Extending support for projects with :test_runner defined with its own :test_prefix, which the adapter won't use due to only looking under :unity.
That currently leads to a discrepancy between what tests are discovered by Ceedling and the test UI.

An easy way of testing the scenario is extending project.yml in the temp_sensor example in the Ceedling project with

:test_runner:
  :test_prefix: Test

:unity:
  :test_prefix: test
  :defines:
    - -RUN_TEST
    - -UNITY_SKIP_DEFAULT_RUNNER

One or both of the defines will force Unity to use Test, hiding the tests in the example project.

---

Currently the README has a link to report issues under this project, but

Issues are disabled for the selected repository

P.S: The big green button after a commit does a different thing in a forked project... 🥲 Sorry for the initial empty PR

[mkarlesky]

@Edoardo-en Thank you for this submission. I think this is a natural consequence of the existing YAML processing mechanism of the extension. As it stands today, the extension duplicates the project configuration YAML processing functionality of Ceedling, but, of course, in a much more simplistic way. PR #12 will form the backbone of the next release of the extension, and it uses Ceedling's own internal YAML processing to eliminate issues like this. We may get to close this PR when that one lands, but I want to investigate to ensure my assessment is correct.

[mkarlesky]

I was able to confirm that the essential problem here was resolved in the 2.0.0 rewrite that closed numerous open issues. The reported problem was real, but new versions of the extension have already fixed it.