Rules and triggers are not created under the package defined in manifest

I noticed that rules and triggers are not created under package defined in manifest. For example, after deploying the cloudant use case ([manifest.yaml](https://github.com/daisy-ycguo/wskdeploy/blob/cloudant-test/tests/src/integration/cloudant/manifest.yaml)), following items will be created. Actions are in package `cloudant-sample`, but rules and triggers are in default package. I think it is a bug and it should be fixed.

```
Entities in namespace: guoyingc@cn.ibm.com_dev
packages
/guoyingc@cn.ibm.com_dev/openwhisk-cloudant private
/guoyingc@cn.ibm.com_dev/cloudant-sample private
actions
/guoyingc@cn.ibm.com_dev/cloudant-sample/process-change-cloudant-sequence private sequence
/guoyingc@cn.ibm.com_dev/cloudant-sample/process-change private nodejs:6
triggers
/guoyingc@cn.ibm.com_dev/data-inserted-trigger private
rules
/guoyingc@cn.ibm.com_dev/log-change-rule private
```

Start with tests/src/integration/cloudant/manifest.yaml and trace the deployment path that creates its rules and triggers. Reproduce the cloudant deployment, inspect the resulting entities, and consider the issue done when those rules and triggers are created under the manifest-defined package alongside the actions.

Written by the indexing model from the issue text.