Fix the VSP update procedure is being rejected by a condition that checks if a VFC being created has the same name, type and vendor release. This was recently introduced to avoid duplicate VFC creation during the initialization process, but it breaks the VSP update that contains a node_type declaration, as the operation is rejected because of the checking, returning an error. 

To reproduce:

1. Onboard a VSP using this package etsi-vnf-virtual-linkable.csar, and
2. Import the VSP. Don't certify.
3. Go to the Catalog Home screen and try to update the VSP (even if it is the same version).
4. And an error should be thrown.