[artifact-manager] (#669) Fix failure during pull of vROPs Policies

[akantchev]

[maven, vrops] (#669) Fixed Problem with Pulling of vROPs Policies.

Description

Fixed problem with pulling of vROPs policies due to missing policiesMetadata.vrops.json file during pull. The manipulation of this file is removed, as it is no longer needed.
When exporting of special type custom groups (dependent on vROPs policies), the name of the policy is stored in the custom group JSON file. When importing those custom groups to vROPs their policies are searched in the target system prior import, if they cannot be found an error will be thrown.

Checklist

• I have added relevant error handling and logging messages to help troubleshooting
• I have added tests that prove my fix is effective or that my feature works
• I have updated the PR title with affected component, related issue number and a short summary of the changes introduced
• I have added labels for implementation kind (kind/) and version type (version/)
• I have tested against live environment, if applicable
• I have my changes rebased and squashed to the minimal number of relevant commits. Notice: don't squash all commits
• I have added a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Testing

Using a project generated by the vROPs archetype that has policies in the content.yaml do:

mvn vrops:pull -P <ENV_NAME>

Pull should be working fine.

Release Notes

When exporting of special type custom groups (dependent on vROPs policies), the name of the policy is stored in the custom group JSON file. When importing those custom groups to vROPs their policies are searched in the target system prior import, if they cannot be found an error will be thrown.

Related issues and PRs

#669