Otel jaeger v2 helm chart along with plater integration

[hyi]

Otel jaeger v2 helm chart along with plater integration.

[hyi]

@EvanDietzMorris I'll update this tag after a new release is created for plater with this PR merged.

[EvanDietzMorris]

Very cool. I haven't tried installing this but the instance at RENCI seems to be working.

I noticed that the values files here do not get encrypted with git-crypt, because they don't match the patterns in https://github.com/helxplatform/translator-devops/blob/develop/.gitattributes

We might want to go ahead and make a renci-values and ncats-values files that contain any secrets or possibly resource allocations we can tweak independently. Otherwise, after we update the plater image, I think we might as well merge this is in as a great first pass.

[hyi]

@EvanDietzMorris Thanks for pointing me to the .gitattributes git-crypt which I totally forgot I might need to update to have the new values file encrypted. After looking into the new values files more carefully, I verified there are no secrets included in the new values file, but a secret yaml file needs to be generated as part of the jaeger setup and deployment process as detailed in the readme file. The main reason is that the elasticsearch helm chart deployment will randomly generate a password secret for handshaking with jaeger, and that value needs to be used to generate a secret value yaml file which will be used for deploying jaeger as part of the user authentication to link to the elasticsearch backend. So we may not need to encrypt the new values files after all.