As an OPS I would like to be able to Get all relevant Configuration information from the Tosca parser, So I will be able to instantiate a configuration

Definition of Done:
1. During service "A la cart " Flow Once the service contains a Node template type = "Configuration" Need to retrieve all the
Configuration metadata
2. For each configuration retrieved, need to get the list of requirements
3. Each requirement has a specific Node linked to it - By saying "node" I mean a node template - which will be type "Service proxy"
4. For each requirement need to get the relevant "Node template" Metadata
5. Need to distinguish between the purpose  "Source" & the "collector" requirements
   - The way to distinguish between the requirements,is by their name for example
        Each Requirement has a Name - for example : "Source" "Collector" :

requirements:
            - source:
                node: abc99af4-0a3f-42ec-af20-bf1455343345_0_proxy # the vMME proxy node
                capability: cap_abc99af4-0a3f-42ec-af20-bf1455343345_04: # source capability #4
            - collector:
                node: abc99af4-0a3f-42ec-af20-bf1455343399_0_proxy # the vProbe proxy node
                capability: cap_abc99af4-0a3f-42ec-af20-bf1455343399_02: # collector capability #2
6. The metadata received should be the same the like in the NF - Any other node template

Please note the following:
1. New Tosca functions were created for above described behavior - See Attached Tosca Parser Spec
2. The Metadata of the configuration Should be displayed in the new designed UI
3.  Each Type of requirement will have a dedicated location based on the design of the UI - Source on the right & Collector on the left

Integration Required:
1. With TOSCA Parser