CI: Don't create port with binding profile

Creating a port with a binding profile now requires a user with the
service role. This fixes CI by removing the tasks which create a port
with a binding profile. The new policy implies that only other openstack
services should be doing this. The capability can remain in the module,
but it is unlikely to be used unless with a custom or deprecated policy.

Change-Id: I89306d35670503d2fc8e76c030d88f64c20eca08

ci/roles/port/defaults/main.yml

@@ -1,6 +1,3 @@
-binding_profile:
-  "pci_slot": "0000:03:11.1"
-  "physical_network": "provider"
 expected_fields:
   - allowed_address_pairs
   - binding_host_id

ci/roles/port/tasks/main.yml

@@ -256,27 +256,6 @@
     state: absent
     name: ansible_security_group
 
-- name: Create port (with binding profile)
-  openstack.cloud.port:
-    cloud: "{{ cloud }}"
-    state: present
-    name: "{{ port_name }}"
-    network: "{{ network_name }}"
-    binding_profile: "{{ binding_profile }}"
-  register: port
-
-- name: Assert binding_profile exists in created port
-  assert:
-    that: "port.port['binding_profile']"
-
-- debug: var=port
-
-- name: Delete port (with binding profile)
-  openstack.cloud.port:
-    cloud: "{{ cloud }}"
-    state: absent
-    name: "{{ port_name }}"
-
 - name: Delete subnet
   openstack.cloud.subnet:
     cloud: "{{ cloud }}"