helm-toolkit dependency resolver may generate incorrect dependencies

[Phil Sphicas]

When multiple resources in a chart have targeted and static dependencies, the dependencies from one resource may be applied to the other resources, instead of the intended static dependencies.

This is best seen by example. In the openstack-helm/neutron chart using the default values.yaml, the expectation is that the `helm template . -x templates/daemonset-ovs-agent.yaml` will reflect the following static dependencies:

    ovs_agent:
      jobs:
        - neutron-rabbit-init
      pod:
        - requireSameNode: true
          labels:
            application: openvswitch
            component: openvswitch-vswitchd
        - requireSameNode: true
          labels:
            application: openvswitch
            component: openvswitch-vswitchd-db
      services:
        - endpoint: internal
          service: oslo_messaging
        - endpoint: internal
          service: network

However, the rendered output gives this, which actually corresponds to the static dependencies of neutron server:

        - name: DEPENDENCY_SERVICE
          value: default:mariadb,default:rabbitmq,default:memcached,default:keystone-api
        - name: DEPENDENCY_JOBS
          value: neutron-db-sync,neutron-ks-user,neutron-ks-endpoints,neutron-rabbit-init
        - name: DEPENDENCY_DAEMONSET
          value: ""
        - name: DEPENDENCY_CONTAINER
          value: ""
        - name: DEPENDENCY_POD_JSON
          value: ""
        - name: DEPENDENCY_CUSTOM_RESOURCE
          value: ""