Remove restrictions when using Helm Chart

At the Yoga release, the following restrictions exist when using the Helm chart:

1. We basically need the k8s cluster created by the Mgmt Driver to use Helm chart.

This is because the `openstack vim register` command cannot add information to access the Helm environment. [1]
To remove this restriction, this blueprint proposes to make it possible to add `extra` field using the `openstack vim register` command or API.
This will allow user to deploy a Helm operator with less steps and support VNF using hardware acceleration (such as GPU, FPGA, ASIC, etc).

2. We cannot create multiple VNF Instances from a single VNF Package when deploying CNF.

This is because the `properties.name` of the VDU defined in the VNFD and the name of the resource actually created must be the same. [2]
To remove this restriction, this blueprint proposes to change adding a parameter to additionalParams in InstantiateVnfRequest to associate the VDU to the actual resource name.

[1] https://docs.openstack.org/tacker/latest/user/mgmt_driver_deploy_k8s_and_cnf_with_helm.html#check-results-of-instantiation-operations
[2] https://docs.openstack.org/tacker/latest/user/mgmt_driver_deploy_k8s_and_cnf_with_helm.html#create-vnfd