chore: refactored log traces for AppInsight tuning

[andrea-deri]

This PR contains some changes made on logs in order to reduce the verbosity at INFO level and, automatically, reduce costs related to Application Insights log monitoring.

List of Changes

• Moved some info logs to debug level
• Refactored setSessionDataInfoInMDC(), moved in MDCUtils as setSessionDataInfo()
• Refactored some log messages

Motivation and Context

This change is made in order to reduce the quantity of not useful logs generated by service.

How Has This Been Tested?

• Tested in local environment
• Tested in DEV environment

Screenshots (if appropriate):

Types of changes

• Chore (non-breaking change which does not change flow or fixes an issue)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[github-actions]

The default action is to increase the PATCH number of SEMVER. Set IGNORE-FOR-RELEASE if you want to skip SEMVER bump. BREAKING-CHANGE and NEW-RELEASE must be run from GH Actions section manually.

[sonarcloud]

Quality Gate failed

Failed conditions
5.7% Duplication on New Code (required ≤ 3%)

See analysis details on SonarCloud