Secret credential name not dynamic preventing multiple deployments per project namespace

ENTMQBR-1648 addressed the core issue of having a dynamic jgroups ping service name. ENTMQBR-2629 recently addressed storing sensitive credentials in a kubernetes secret.

Now when testing deployment of two statefulsets, with different APPLICATION_NAME's and thus ping service names, we see that the second can not start pods as they cannot file the correct credential secret OOTB.

The cause needs to evaluated and addressed so that we can provide this functionality.