Configure m2, m3, stg cluster access tokens, update periodic reports logic

Currently the logic of obtaining OC client from the cluster and getting deployment verison has been all squashed to m1 cluster directly.

In the future we want this to be cluster-specific.

I need to set up access tokens for m2, m3 and stg clusters, put them into crw-jenkins and update the pipelines