Adjust LE role file matchers on system-config-run-* jobs

The LetsEncrypt roles match on a number of jobs to ensure reasonable
coverage. Unfortunately, they were matching gitea and gerrit jobs. These
are problematic choices due to their extended runtime. The matches for
static and mirror are probably sufficient to test general apache
integration.

That said gitea has a special LE handler for handling service restarts.
We add a special file matcher just for that file on the gitea job.
Graphite also has a similar handler but had no file matcher. Add it.

The goal here is to reduce the turn around time on replacing servers. It
is common to have to edit LE configuration (particularly handlers) when
adding and removing servers and if we are testing gitea and gerrit each
time this is slow.

Change-Id: Iaa9b0fd61853679629915feffec8ffbf5fb65f68

zuul.d/system-config-run.yaml

@@ -708,7 +708,6 @@
       - playbooks/roles/apache-ua-filter/
       - playbooks/roles/pip3/
       - playbooks/roles/install-docker/
-      - playbooks/roles/letsencrypt
       - playbooks/roles/gerrit/
       - playbooks/roles/gitea.*
       - playbooks/roles/haproxy/
@@ -786,6 +785,7 @@
       - playbooks/service-graphite.yaml
       - playbooks/roles/graphite
       - playbooks/roles/install-docker/
+      - playbooks/roles/letsencrypt-create-certs/handlers/restart_graphite.yaml
       - playbooks/roles/pip3/
       - testinfra/test_graphite.py
 
@@ -1091,7 +1091,6 @@
       - playbooks/roles/run-selenium/
       - testinfra/util.py
       - playbooks/roles/install-docker/
-      - playbooks/roles/letsencrypt
       - playbooks/roles/gerrit/
       - playbooks/zuul/gerrit/
       - playbooks/zuul/templates/host_vars/review99.opendev.org.yaml.j2