SO NFVO NBI API Handler needs to enhance its Instantiate NS to ETSI 3.3.1 from ETSI 2.7.1

• Leveraging ETSI 3.3.1 swagger upgrade, upgrade the Instantiate NS NBI code to support 3.3.1
• Follow and confirm 3.3.1 changes on the message sequencing, request, response, pre- and post-conditions.
• Preconditions:
  • NS instance is NOT_INSTNANTIATED state
  • SOL007 NS packages are stored in ETSI Catalog Manager.
  • the Cli-based SO NFVO Client is ready to send the SOL005-compliant Instantiate NS request
  • The SO-NFVO (so-etsi-nfvo) pod is ready
• Test the following scenarios: 
  • Supports the SOL005-compliant Instantiate NS API 
    • Supports Instantiate NS request API: POST /api/nslcm/v1/ns_instances/{nsInstanceId}/instantiate (InstantiateNsRequest)
    • Supports responses 202 Accepted with an empty payload body

• • • • Returns a dummy 202 until the backend business logic is ready 
    • Supports NS Lifecycle Operation Occurrence Notification
      • Use a Location HTTP header that points to the new individual NS Lifecycle Operation Occurrence resource; i.e. the URI of that resource (.../ns_lcm_op_occs/{nsLcmOpOccId}
      • Supports the Sends nsLcmOperationOccurrenceNotifiation (start, result) notification operation until the result status becomes COMPLETED
    • Optionally, Instantiate NS operations uses the GET individual NS LCM operation occurrence request and response
    • Error handling: if the operation is failed, error information is provided in the notification message

• Post conditions: the NS Instance is as the INSTANTIATED state

Note: secure communication is handled by a separate user story, SO-3165.