Cleanup iweb/inap provider content

This provider is going away and the depends-on change should be the last
step to remove it from nodepool. Once that is complete we can stop
trying to manage the mirror there (it will need to be manually shut
down), stop managing our user accounts, and stop writing cloud.yaml that
include these details for inap/iweb on nodepool nodes.

Note we leave the bridge clouds.yaml content in place so that we can
manually clean up the mirror node. We can safely remove that clouds.yaml
content in the future without much impact.

Depends-On: https://review.opendev.org/c/openstack/project-config/+/867264
Change-Id: I01338712aeae79aa78e7f61d332a2290093c8a1b

inventory/service/group_vars/bastion.yaml

@@ -199,20 +199,6 @@ cloud_launcher_clouds:
       - openstackci-keypairs
       - openstackci-security
 
-  # iweb
-  - name: openstackci-iweb-mtl01
-    oscc_cloud: openstackci-iweb
-    region_name: mtl01
-    profiles:
-      - openstackci-keypairs
-      - openstackci-security
-  - name: openstackjenkins-iweb-mtl01
-    oscc_cloud: openstackjenkins-iweb
-    region_name: mtl01
-    profiles:
-      - openstackci-keypairs
-      - openstackci-security
-
   # vexxhost
   - name: openstackci-vexxhost-mtl1
     oscc_cloud: openstackci-vexxhost