Improve communication of no debugger support when board+programmer supports debugging, but custom options is misconfigured

[kittaakos]

Describe the request

It's a follow-up of #14 based on the remark from @pillo79 made at #2342 (comment):

Just out of curiosity, what does that text say in the case of the Nano ESP32 with the wrong "USB mode"?

To detect whether the debugging feature is enabled, IDE2 uses the CLI's IsDebugSupportedRequest. The request must contain the FQBN of the currently selected board and the selected programmer ID. However, the FQBN might contain additional config options. In some cases, the config options (attached to the FQBN) are the tiebreaker. For example, the debugger is supported when the FQBN is esp32:esp32:nano_nora:USBMode=hwcdc and the programmer is esptool, but it's unsupported when the USBMode=hwcdc is missing from the FQBN.

I found it helpful if IDE2 could tell users that the debugger is supported, but they must select the Debug Mode (Hardware CDC) instead of the Normal Mode (TinyUSB) USB Mode board config option.

Describe the current behavior

As noted at #2342 (comment), the IDE2 says Debugging is not supported by 'Arduino Nano ESP32' but nothing more:

Just out of curiosity, what does that text say in the case of the Nano ESP32 with the wrong "USB mode"?

That's a good point. It just says that Debugging is not supported by 'Arduino Nano ESP32'. The CLI cannot provide more information when asked via the arduino-cli debug check command. It only tells whether it's supported or not. IDE2 says to the user what the CLI says.

Arduino IDE version

763fde0

Operating system

macOS

Operating system version

14.2.1

Additional context

This task likely requires CLI changes

Issue checklist

• I searched for previous requests in the issue tracker
• I verified the feature was still missing when using the latest nightly build
• My request contains all necessary details