OpenTelemetry Support

[RohitRanjanMS]

Enhancing the DotNet Worker with OpenTelemetry Support involves two key changes aimed at improving telemetry integration and traceability:

Context Propagation
Introduced a foundational Activity serving as the precursor to the "Invoke" activity or any customer-generated activity. This foundational activity emulates the remote activity in the Host process, enabling the correlation of all logs and traces with the server/consumer telemetry emitted by the host process.

OpenTelemetryBuilder extension method for Azure Functions
a. Functions Resource Detector - This component automatically detects and applies a set of standard attributes defined by the OTel Spec to the telemetry data.
b. Worker Capability - To signal the Host to disregard any logs produced by the worker process.

.ConfigureServices(s =>
{
   s.AddOpenTelemetry()
    .UseFunctionsWorkerDefaults()
    .UseAzureMonitor();
})

Reverse Proxy Scenario

Client Telemetry from Console App
-- -> Console App Outgoing Request
-- -- -> Functions Host Incoming Request
-- -- -- -> Functions Host Outgoing Request
-- -- -- -- -> DotNet Worker Incoming Request
-- -- -- -- -- -> Outgoing Request to bing.com from Worker 

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

Made the change locally and pushed.