Add AMHandler to connect to Internet2 via Virtual Networks

[zlion]

Tasks:

• 1. Experiment with Virtual Networks API commands for setting up L3VPN Connections for Cloud Connect
• 2. Create Ansible playbooks for Virtual Networks connection service
• 3. Design Virtual Networks sliver model
• 4. Add virtual_network_handler.py to handle the Cloud Connect sliver and invoke the Ansible playbooks

[zlion]

Over the past few weeks, I've been collaborating with Christopher and the Internet2 team to refine the workflows for AWS, GCP, and FABRIC. Here are the key updates:

1. We have reached a consensus on the high-level design of these workflows. Notably, we've confirmed that the Insight console workflow allows for completion without requiring additional feedback from the AWS console.
2. I've successfully conducted tests on the API access keys, and they are functioning as expected.
3. I've made initial attempts to establish connections with cloud providers. However, I was unable to complete the entire testing process due to the fact that certain aspects of cloud provisioning are still in development. I anticipate that these tests can be successfully executed following the scheduled launch date of the Insight Console.
4. Regarding connections to FABRIC, it's worth noting that the BGP (Border Gateway Protocol) configuration is not yet finalized. I will proceed with testing as soon as I receive updates from them.

[zlion]

The code development comes to the milestone that we have the L3 connection functionality ready for integration tests. Will focus on resolving issues found during the integration tests.

[zlion]

Issues:

• 1. NSO error communication with router

 I encountered an error during creating L3 connection via API.
  "provisioningState": "ERROR",
  "provisioningDetails": "[2023-12-08T23:29:37+00:00] [AWS] [PENDING] - Connection ordered, login to your AWS console to accept\n[2023-12-08T23:29:41+00:00] [NSO] [ERROR] - NSO error communicating with router",

I did take a look last night, it was an NSO sync issue. There are some improvements that we needed to make about retrying transient failures more quickly but with a back off of some sort instead of an hourly job

[zlion]

Some issues found in the integration tests:

• 1. The VLAN tag management code need to be revisited as we saw tags could be reused. Komal is on it.
• 2. AMHandler should report errors with more details. I will look into the APIs again to pull as much information as possible.
• 3. Deleting a connection with error provision status is still a trouble. Internet2 engineers promise to fix it.