Only show tool warning if trying to use built-in tools

[jreineckearm]

Fixes

• [Bug]: Warning pops up when using an absolute path in the launch config #407

Changes

• Fixing condition under which to show the warning that built-in tools are not present in extension installation.
• Slightly refine warning message, should never be visible in healthy user installation.
• Without the fix, you were able to see warning notifications popping up in the bottom right if you used an absolute path for gdb or pyocd in the launch config. Even if the paths were valid and connections happened.

Screenshots

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).

[qltysh]

All good ✅

[qltysh]

Diff Coverage: The code coverage on the diff in this pull request is 100.0%.

Total Coverage: This PR will increase coverage by 0.36%.

File Coverage Changes

Path	File Coverage Δ	Indirect
src/debug-configuration/gdbtarget-configuration-provider.ts	-2.8
src/debug-configuration/subproviders/pyocd-configuration-provider.ts	1.2
src/desktop/tool-path-utils.ts	100.0

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[jreineckearm]

@thorstendb-ARM , would you mind a review?

[thorstendb-ARM]

LGTM

[jreineckearm]

@soumeh01 , looks like qlty check timed out/failed again. Are there known issues with these services? It looks like it recovers on rerun.

[soumeh01]

@soumeh01 , looks like qlty check timed out/failed again. Are there known issues with these services? It looks like it recovers on rerun.

Nothing that I am aware of.