Add "cortex-debug.objdumpPath" option to settings.json

Context

I am working on a project that uses the xPack package system to install the arm-gcc-none-eabi toolchain. xPack creates shims to the executable files (see https://xpack.github.io/).

Current functionality

For vscode on Windows, I have to specify the extensions .cmd for any vscode extension to correctly use the arm binary tools (e.g. ms-vscode.makefile-tools and marus25.cortex-debug).

In coretex-debug, the gdb path can be set using the option:

"cortex-debug.gdbPath.windows": "${workspaceFolder}/xpacks/.bin/arm-none-eabi-gdb.cmd"

This option works as expected.

Current problem

Without the ability to set the arm-none-eabi-objdump path, the coretex-debug extension is unable to populate the static and global variables in a debug session.

Manual fix

Copying arm-none-eabi-objdump.exe into the path specified in cortex-debug.armToolchainPath resolved the issue. This is not ideal as the project installation will no longer be automated.

Requested functionality

Would it be possible to add the option cortex-debug.objdumpPath to settings.json (and launch.json)? This would serve as a companion to the already existing cortex-debug.gdbPath option.

For my project, the option would take the value:

"cortex-debug.objdumpPath.windows": "${workspaceFolder}/xpacks/.bin/arm-none-eabi-objdump.cmd",

[PhilippHaefele]

According to latetst changelog (prerelease version V1.1.8) this is fixed

Feature: you can now customize the objdumpPath like you can the gdbPath you your settings or in launch.json

[haneefdm]

Welcome. Keep up the good work. I see a few people using xPack (when they submit issues with their launch.json).