[New Feature] Allow bash environment variable to be used in configuration

[gaodingpan]

Currently, when configuring C/C++ include/browse or dotconfig paths, bash environment variables are not allowed, only vscode variables like ${workspaceFolder} can be recognized. This can be a bit troubling when there are multiple dotconfig paths(using bash environment variable to distinguish different options, e.g debug build/release build) in the same workspace. Support of using bash environment variable to configure such paths is much desired.

[Colengms]

Hi @gaodingpan . Thanks for suggesting this. We will consider this for our backlog. Upvotes would increase its priority.

[github-actions[bot]]

This feature request is being closed due to insufficient upvotes. Please leave a 👍-upvote or 👎-downvote reaction on the issue to help us prioritize it. When enough upvotes are received, this issue will be eligible for our backlog.