Remove ctlplane-subnet from example file.

The check expects that we have the ctlplane network.
Including the subnet as well might cause issues with
the current check implementation:

https://opendev.org/openstack/tripleo-ansible/src/branch/master/tripleo_ansible/ansible_plugins/modules/tripleo_baremetal_expand_roles.py#L95-L102

Full discussion is on: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/841114

Change-Id: I93ad750ffb1677145d6f0954d9e4e0c000d2b41e

baremetal-samples/baremetal_deployment.yaml

@@ -10,7 +10,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.10
     - network: external
       subnet: external_subnet
@@ -30,7 +29,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.11
     - network: external
       subnet: external_subnet
@@ -50,7 +48,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.12
     - network: external
       subnet: external_subnet
@@ -76,7 +73,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.20
     - network: external
       subnet: external_subnet
@@ -94,7 +90,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.21
     - network: external
       subnet: external_subnet
@@ -112,7 +107,6 @@
     managed: true
     networks:
     - network: ctlplane
-      subnet: ctlplane_subnet
       fixed_ip: 192.168.24.22
     - network: external
       subnet: external_subnet