Alternative Contexts not recognised when serverType=SASVIYA

[Allan Bowe]

When creating a projectTarget in the VS Code extension, we supply a default compute context

When this context is changed, it is not possible to deploy (403 error)

"good" target:

    {
      "name": "v7",
      "serverUrl": "https://sas.com",
      "serverType": "SASVIYA",
      "appLoc": "/Public/app/v7",
      "contextName": "SAS Job Execution compute context"
    }

"bad" target:

    {
      "name": "v7",
      "serverUrl": "https://sas.com",
      "serverType": "SASVIYA",
      "appLoc": "/Public/app/v7",
      "contextName": "Reusable-Compute-Context"
    }

Expected behaviour: Valid contexts should be picked up and used when connecting to Viya