Fix VSP update backend process

Fix VSP update backend process

Fix the VSP update procedure which was 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.
This change adds a condition to confirm that no VSP CSAR is involved,
before trying to check for the name, type and vendor release.

Change-Id: Ie46195e810cd72f7412acc7cb01a764ef010f58d
Issue-ID: SDC-3561
Signed-off-by: André Schmid <andre.schmid@est.tech>