cleanup(inventory): Drop support for multiple connections

The support for connections to multiple clusters in the inventory
plugin is dropped to better align with user expectations and how other
inventories work. If inventories of multiple clusters are needed the
inventory can be run multiple times with different configurations.
This also helps to clean up the code and make it simpler.

For now this adds a compatibility helper so that configurations with a
single connection entry remain supported and a warning is emitted.

Signed-off-by: Felix Matouschek <fmatouschek@redhat.com>

tests/integration/targets/inventory_kubevirt/test.kubevirt.yml

@@ -1,7 +1,6 @@
 ---
 plugin: kubevirt.core.kubevirt
-connections:
-  - name: test
-    namespaces:
-      - default
-    create_groups: true
+name: test
+namespaces:
+  - default
+create_groups: true

tests/integration/targets/inventory_kubevirt/test.label.kubevirt.yml

@@ -1,7 +1,6 @@
 ---
 plugin: kubevirt.core.kubevirt
-connections:
-  - namespaces:
-      - default
-    create_groups: true
-    label_selector: app=test
+namespaces:
+  - default
+create_groups: true
+label_selector: app=test

tests/integration/targets/inventory_kubevirt/test.net.kubevirt.yml

@@ -1,7 +1,6 @@
 ---
 plugin: kubevirt.core.kubevirt
-connections:
-  - namespaces:
-      - default
-    create_groups: true
-    network_name: bridge-network
+namespaces:
+  - default
+create_groups: true
+network_name: bridge-network

tests/integration/targets/kubevirt_vm/test.kubevirt.yml

@@ -1,6 +1,5 @@
 ---
 plugin: kubevirt.core.kubevirt
-connections:
-  - namespaces:
-      - default
-    network_name: bridge-network
+namespaces:
+  - default
+network_name: bridge-network