Launch Target doesn't initialise the shell as per the user's config

Brief Issue Summary

In my case, I'm using MSYS2 for my default terminal:

    "terminal.integrated.profiles.windows": {
        "MSYS2": {
            "path": "C:/Tools/msys64/usr/bin/bash.exe",
            "label": "MSYS2",
            "args": ["--login", "-i"],
            "env": {
                "MSYSTEM": "MSYS2",
                "CHERE_INVOKING": "1",
                "MSYS2_PATH_TYPE": "inherit"
            }
        },
    },
    "terminal.integrated.defaultProfile.windows": "MSYS2",

I rely on these arguments in order to pick the correct MSYS shell and to bring over the path variables (especially important for running my program after compiling, as without "inherit" being defined the path starts from a flash slate).

It seems like CMake Tools only retrieves and utilises the shell path, ignoring the rest of the user's configuration for that shell. I haven't found any means to configure this and it essentially renders the Launch Target feature useless for anyone who has a non-trivial shell setup.

CMake Tools Diagnostics

No response

Debug Log

No response

Additional Information

The terminal instance created by Launch Target:

ic2000@Win11 MSYS ~
$ "C:/Users/ic2000/Documents/Projects/Test/build/Release/src/test.exe"
C:/Users/ic2000/Documents/Projects/Test/build/Release/src/test.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory

The terminal instance created by VS Code, properly utilising my terminal configuration:

ic2000@Win11 MSYS2 ~
$ "C:/Users/ic2000/Documents/Projects/Test/build/Release/src/test.exe"
Known pipe types:
  wglGraphicsPipe
(all display modules loaded.)

https://github.com/microsoft/vscode-cmake-tools/commit/d9557e68f4b08983414ef45ea08caa8523c68f28 is how I've personally got around this for the meantime.

Start by reviewing the Launch Target terminal setup and the workaround commit d9557e68f4b08983414ef45ea08caa8523c68f28. Reproduce the issue with the MSYS2 profile shown in the report, then verify that Launch Target honors the configured shell arguments and environment variables, including MSYSTEM, CHERE_INVOKING, and MSYS2_PATH_TYPE.