wsk project deploy fails if ~/.wskprops files defines a namespace

This is based on work related https://github.com/apache/incubator-openwhisk-catalog/pull/268.
To reproduce, create a ~/.wskprops file like this, for example:

```
> cat ~/.wskprops
APIHOST=localhost
AUTH=23bc46b1-71f6-4ed5-8c54-816aa4f8c502:123zO3xZCLrMN6v2BKK1dXYFpXlPkccOFqm12CdAsMgRU4VrNZ9lyGVCGuMDGIwP
INSECURE_SSL=true
NAMESPACE=guest
```

Then try to run `wsk` to project deploy. The cli is picking up the NAMESPACE property and trying to install actions in the wrong namespace. This will fail since the key on the command line does not match. AFAIK there is no way to override the namespace property from the command line.

```
Info: The API host is [172.17.0.1], from wskdeploy command line.
Info: The auth key is set, from wskdeploy command line.
Info: The namespace is [guest], from .wskprops.
```

which later leads to errors like:
```
Error: Deployment did not complete sucessfully. Run `wskdeploy undeploy` to remove partially deployed assets.
servicedeployer.go [1660]: [ERROR_WHISK_CLIENT_ERROR]: Error code: 147: The supplied authentication is not authorized to access 'guest/watson-textToSpeech'. (code 702f9dfbfc752ee58b0546d6a15d6cb2): HTTP Response Status: 403 Forbidden HTTP Response Body: {"code":"702f9dfbfc752ee58b0546d6a15d6cb2","error":"The supplied authentication is not authorized to access 'guest/watson-textToSpeech'."}
```