User-level server setting in objectscript.conn should not trump a workspace-level docker-compose setting

[gjsjohnmurray]

To reproduce the issue, have a workspace-level objectscript.conn setting whose docker-compose points to a container:

    "objectscript.conn" :{
      "ns": "USER",
      "username": "SuperUser",
      "password": "SYS",
      "docker-compose": {
        "service": "iris",
        "internalPort": 52773
      },
      "active": true
    }

Confirm that the connection is active.

In the user-level settings add an objectscript.conn that points to a server defined in intersystems.servers:

	"objectscript.conn": {
		"active": true,
		"server": "iris201",
		"ns": "USER"
	},

When you save this, the extension incorrectly tries to connect to the named server in preference to the target container specified in the workspace-level docker-compose setting object.

I will provide a PR.