Drop fedmsg_qa_network concept

I don't think this is needed any more. openQA publishes natively
to fedora-messaging these days, and these groups never have done
anything there. ResultsDB still publishes to fedmsg, it seems,
but the new instances were not added to these groups and I don't
think we need/want to do that, we should just make sure they
have the necessary access via other more widely-used groups if
anything. (It seems like the restrictions these groups used to
affect have been - possibly temporarily - removed entirely at
present, but we can figure out any necessary changes there if the
restrictions are restored).

Signed-off-by: Adam Williamson <awilliam@redhat.com>

filter_plugins/fedmsg.py

@@ -9,7 +9,7 @@ def invert_fedmsg_policy(groups, vars, env):
     """
 
     if env == 'staging':
-        hosts = groups['all'] + groups['staging'] + groups['fedmsg_qa_network_stg']
+        hosts = groups['all'] + groups['staging']
     else:
         hosts = [h for h in groups['all'] if h not in groups['staging']]
 

inventory/inventory

@@ -786,19 +786,6 @@ wiki01.iad2.fedoraproject.org
 
 [zanata2fedmsg]
 
-# This is a convenience group listing the hosts that live on the QA network that
-# are allowed to send inbound fedmsg messages to our production fedmsg bus.
-# See also:
-# - inventory/group_vars/proxies for the iptables custom_rules list
-# - roles/fedmsg/base/templates/relay.py.j2
-# - filter_plugins/fedmsg.py
-[fedmsg_qa_network]
-retrace01.qa.fedoraproject.org
-resultsdb01.qa.fedoraproject.org
-
-[fedmsg_qa_network_stg]
-resultsdb-stg01.qa.fedoraproject.org
-
 # assorted categories of fedmsg services, for convenience
 [fedmsg_hubs:children]
 badges_backend