Implement a workaround to open login terminals on remote connections to compute instances

[sevillal]

In Azure ML Studio terminal conda activate works out of the box. We identified that conda activate does not work out of the box when connected to a compute instance with VS Code, user needs to run conda init first or source /etc/profile.

From this issue looks like it is a problem with remote extensions.

We can work around it by manually changing the remote settings.json with:

{
    "terminal.integrated.defaultProfile.linux": "bash",
    "terminal.integrated.profiles.linux": {
        "bash": {
            "path": "bash",
            "icon": "terminal-bash",
            "args": ["-l"]
        }
    }
}

[tbombach]

Affects other remote experiences - let's discuss with VS Code about a solution that doesn't just patch our experience