Use OpenTelemetry tooling for diagnostics setup

[sigridbra]

Part of an ongoing work to export data for logging, monitoring, and tracing to Azure Monitor Telemetry for all of our applications.

Note that this setup will cause changes in log-levels for the following namespaces:

Console
Microsoft, LogLevel.Warning -> Information
System, LogLevel.Warning -> Information

ApplicationInsights:
Program.cs, LogLevel.Trace -> Warning

Related Issue(s)

#136

Verification

• Your code builds clean without any errors or warnings
• Manual testing done (required)
• Relevant automated test added (if you find this hard, leave it and we'll help out)
• All tests run green

Documentation

• User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

[sigridbra]

Not removing package here as this is needed for tracking db performance. It's extracted into it's own issue https://github.com/Altinn/team-core-private/issues/165

[SandGrainOne]

Not sure about the placement. AddAzureMonitorTelemetryExporters isn't called unless we have an applicationInsightsConnectionString.

[SandGrainOne]

Forget it. I finally understood the purpose. Looks fine except the order. Documentation emphasis adding the processor before the call to AddAzureMonitorTraceExporter.

[SandGrainOne]

Would this work?

Suggested change

	services.ConfigureOpenTelemetryTracerProvider(tracing => tracing
	.AddAzureMonitorTraceExporter(o =>
	{
	o.ConnectionString = applicationInsightsConnectionString;
	})
	.AddProcessor(new DependencyFilterProcessor()));
	services.ConfigureOpenTelemetryTracerProvider(tracing => tracing
	.AddProcessor(new DependencyFilterProcessor())
	.AddAzureMonitorTraceExporter(o =>
	{
	o.ConnectionString = applicationInsightsConnectionString;
	}));

[sonarqubecloud]

Quality Gate failed

Failed conditions
63.16% Condition Coverage on New Code (required ≥ 65%)

See analysis details on SonarQube Cloud