Authentication for metrics and version endpoint

[naveenpaul1]

Explain the changes

1. Call CreateAuthAPI rpc with a role metrics-auth to get the JWT token in the configuration phase, And the response token will be saved as secret(metrics-auth-secret)
2. JWT is signed using the existing signature key JWT_SECRET that used to sign other admin and operator credentials.
3. Secret will be used for authorization for both noobaa management and s3 ServiceMonitor.

Issues: Fixed #xxx / Gap #xxx

1. RHSTOR-7202
   DFBUGS-1802

Testing Instructions:

containerized deployment

1. The customer should be able to access the bearer token from the secret metrics-auth-secret, secret can be used for accessing noobaa management and endpoint metrics/version.

JWT_TOKEN=$(oc get secret/{token-secret-name} -n {namespace} -o jsonpath={.data.metrics_token} | base64 -d)    
curl -k -H "Authorization: Bearer ${JWT_TOKEN "https://{endpoint-loadbalancer-ingress-ip}:{endpoint-port}
curl -k -H "Authorization: Bearer ${JWT_TOKEN}" https://$(oc -n {namespace} get route noobaa-mgmt -o jsonpath='{.status.ingress[*].host}/version or metrics endpoints')

2. Verify all the noobaa specific targets are up and scraping metrics from those tragets in kubernates/ODF

Design doc : https://ibm.ent.box.com/notes/1853310270159

• Doc added/updated
• Tests added