Skydive Integration

**Additional context**
This stack appears to be very similar in its data flow and analysis semantic to the Skydive platform, used to discover/map/manage complex SDN environments such as OpenStack deployments.
It would be very handy to double-up the ThreatMapper agent as a skydive agent and provide console integration for their data as the graphql semantic for traversing their network topologies is very handy in figuring out attack paths. I'm not huge on Go (:crab:), but from what i understand of its dependency structure, such an integration should be feasible without permanently merging the code-bases via dependency management.

**Components/Services**

- [x] UI/Frontend
- [X] API/Backend
- [X] Agent
- [X] Deployment/YAMLs
- [X] CI/CD Integration
- [X Other (third party integration)

The issue names no files, tests, or entry points. Begin by defining the integration boundaries for a Skydive-compatible agent and console data flow; done would mean the requested agent, console integration, deployment/YAML changes, and CI/CD integration are implemented.

Written by the indexing model from the issue text.