Description of problem:
I realized after we added the bugzilla refresh RFE that we probably can re-use the bugzilla email as a retrace-admin email.  So this RFE is two fold:


1. Add a retrace-server.conf parameter to configure an email address for critical problems in retrace-server that may not be noticed by an admin


2. Add a notification if bugzilla login fails in the bugzilla refresh feature.

+++ b/src/retrace-server-bugzilla-refresh
@@ -0,0 +1,60 @@
...
+
+        if bz_user and bz_password:
+            bzapi.login(bz_user, bz_password)
+
+        if bzapi.logged_in:
+            log.write("Successfuly logged in as {0}.\n".format(bz_user))
+        else:
+            log.write("Not logged in. Continue as anonymous user.\n")  <---------- EMAIL ADMIN

This is a critical error since it may end up that someone changes the password or bugzilla fails for some reason and as a result, vmcores associated with bugzillas may get cleaned up incorrectly.


Version-Release number of selected component (if applicable):
upstream 71c67f2e9180e1b49467c8c9dfbfd15de8ddcda9

How reproducible:
easy

Steps to Reproduce:
1. misconfigure password for bugzilla account
2. run retrace-server-bugzilla-refresh

Actual results:
A log message is written to bugzilla_refresh.log but this won't be visible to admins.


Expected results:
Admin should get easily notified of critical problems (not log spam just serious issues).


Additional info:
There may be another answer to monitoring for failures by monitoring various retrace-server log files, so maybe this feature is overkill but not sure.