Basic filtering in /api/infrastructure-monitoring/topology

Currently we're using /api/infrastructure-monitoring/topology to retrieve the list of a subset of the infrastructure snapshots and their relations. The problem is that this endpoints returns everything, and therefore produces massive responses from which we drop most of the data.

In our case, we'd greatly benefit from having a plugins query parameter that contains a list of plugins and that would have the following effect:

• filter the list of nodes to only include snapshots which plugin is in the list of requested plugins

• filter the list of edges to only include edges between snapshots that are included in nodes

For example, assuming that the unfiltered response would have been

GET /api/infrastructure-monitoring/topology

{
  "nodes": [
    {
      "id": "D",
      "plugin": "kubernetesDeployment",
      ...
    },
    {
      "id": "N",
      "plugin": "kubernetesNamespace",
      ...
    },
    {
      "id": "C",
      "plugin": "kubernetesCluster",
      ...
    }
  ],
  "edges": [
    {
      "source": "D",
      "destination": "N",
      "relation": "in"
    },
    {
      "source": "D",
      "destination": "C",
      "relation": "of"
    },
    {
      "source": "N",
      "destination": "C",
      "relation": "of"
    }
  ]
}

A filtered response would have looked like

GET /api/infrastructure-monitoring/topology?plugins=kubernetesDeployment,kubernetesNamespace

{
  "nodes": [
    {
      "id": "D",
      "plugin": "kubernetesDeployment",
      ...
    },
    {
      "id": "N",
      "plugin": "kubernetesNamespace",
      ...
    }
  ],
  "edges": [
    {
      "source": "D",
      "destination": "N",
      "relation": "in"
    }
  ]
}