https://grantadesign.atlassian.net/browse/MI-21691

Preface - Given the datadog instance is managed by Ansys devOps, and datadog is used by other teams as well, we are limited in what we can do. For instance, we cannot create pipelines to extract data directly from logs but instead must rely on tags.

This PR includes the following:

• materialsCustomerObject field changed from apiKey to userId. The apiKey field was not actually used anywhere, while at the same time we needed something to identify users. Given the dashboard might be accessible to a few people, we probably dont want to use customer name or api key, but we can use userId. The userID is assigned (as workflow global variable) after the apiKey is authenticated.

• Given the preface, we now added token count and response time as ContextKey to the logs. We can pickup the ContextKey directly when creating charts.

• When creating a chid span, do not log it as the info logged is redundant. Now both test and production logs are much cleaner.

Debug level (i.e. Test) logs now look like this

Info level (i.e. Production) logs now look like this

• PMs mentioned we do want to log in production this logging.Log.Infof(ctx, "No valid criteria found in any response")

• Added a production log line for when a customer is succesfully authenticated