1. Get the admin_user/passwd/tenant from seperate UI auth config file.
    This will be used only in middleware for recurrent jobs, in case of jobs
    which gets kick started upon restart of jobServer, but due to not logged in
    user, API Server response always gets failed if multi_tenancy is enabled,
    so though we are starting jobs at init time, but we do not get much info,
    only from OpServer. So at init time also read this config file, and get the
    token from keystone and communicate with API Server. Once token gets
    expired, then also use the same user auth to get new token. In case the user
    auth file does not exist or auth does not get succeed, return error to
    client.
2. Once authentication occurs, then after getting new token, store that new
    token against job name, when the job is rescheduled then check if there is any
    registered job task data change, if so, then before recreating new job, update
    the taskdata with all the changed parameters, in this case, we change the
    authObj and tokenObjs in jobData which is used for next time auth to API Server.
3. After purging all redis DBs only, start jobSrever's other tasks.
4. Removed some unwanted log messages.
5. Reissuing of auths using username and password are managed now in jobServer
    only.
6. Do not delete the pubChannel entry if the job is recurrent job, as this may
    be required for redirectToLogout utility.

Change-Id: I78c4aaabfa8c2199e854c7f98dcf52c94b7b257c
Merge "1. Get the admin_user/passwd/tenant from seperate UI auth config file.     This will be used only in middleware for recurrent jobs, in case of jobs     which gets kick started upon restart of jobServer, but due to not logged in     user, API Server response always gets failed if multi_tenancy is enabled,     so though we are starting jobs at init time, but we do not get much info,     only from OpServer. So at init time also read this config file, and get the     token from keystone and communicate with API Server. Once token gets     expired, then also use the same user auth to get new token. In case the user     auth file does not exist or auth does not get succeed, return error to     client. 2. Once authentication occurs, then after getting new token, store that new     token against job name, when the job is rescheduled then check if there is any     registered job task data change, if so, then before recreating new job, update     the taskdata with all the changed parameters, in this case, we change the     authObj and tokenObjs in jobData which is used for next time auth to API Server. 3. After purging all redis DBs only, start jobSrever's other tasks. 4. Removed some unwanted log messages. 5. Reissuing of auths using username and password are managed now in jobServer     only. 6. Do not delete the pubChannel entry if the job is recurrent job, as this may     be required for redirectToLogout utility."