VS Code 'terminal.integrated.env.*' settings not taken into account for 'miDebuggerPath'

Environment

• OS and version: Ubuntu 20.04.6 LTS (Focal Fossa)
• VS Code: 1.85.1
• C/C++ extension: 1.18.5

Bug Summary and Steps to Reproduce

Bug Summary:

The terminal.integrated.env.* VS Code settings are not taken into account for the miDebuggerPath option default value.

This creates some discrepancy between the GDB program that can be run from a VS Code Terminal for this workspace and the one actually used by the extension.

My suggestion would be to take into account the terminal.integrated.env.* VS Code settings while computing the default GDB program, when miDebuggerPath is not explicitly configured in the launch.json file.

Steps to reproduce:

1. Open the reproducer
2. Modify terminal.integrated.env.linux setting to set the PATH environment variable to custom GDB installation
3. Launch the C/C++ debugger (C++ Launch in the Debug Panel)
4. Problem: the GDB used by the extension (with the version displayed in the Debug Console) will not match the one available from a VS Code Terminal

Debugger Configurations

All the needed configuration files are in the `.vscode` folder of the following archive:

[cpp_project.zip](https://github.com/microsoft/vscode-cpptools/files/13905675/cpp_project.zip)

Debugger Logs

No logs

Other Extensions

No response

Additional Information

No response

Start with the reproducer's .vscode configuration and launch.json, then run the C++ Launch configuration and compare the GDB version in the Debug Console with the one available from the VS Code Terminal. Done means terminal.integrated.env.linux, including a custom PATH, affects the default miDebuggerPath when launch.json does not set it explicitly.