feat: add flags for live metrics and w3c tracing + URI filtering

[fmaule]

New config flags (defaulted to false)

• liveMetrics (boolean): enable/disable the live metrics stream for insights: https://docs.microsoft.com/en-us/azure/azure-monitor/app/live-stream
• traceW3C (boolean): enable/disable correlation via W3C: https://docs.microsoft.com/en-us/azure/azure-monitor/app/correlation

URI filtering via telemetry processor

• ignoreURI (default []]) is an strings array of URIs to be ignored: telemetry won't be sent for that specific request (eg. we're skipping logs for __/manifest)

[fmaule]

On second thought, it might be better to have a more conservative default for the ignoreURI to avoid breaking changes.
Let me know if I should also bump the version.

[neodmy]

@Betisman @jgleal anyone with the right privileges you know of could merge and release the changes? Thanks

[fmaule]

I'd suggest to bump the major to v1 just to be 100% sure nothing breaks.

We're testing the change internally in our fork and looks like the insights SDK is behaving slightly differently, we had to disable it during tests in a more specific way than what we used to be, but it might just be flaky tests on our side.

Happy to provide more context/discuss if needed.

[neodmy]

I'd suggest to bump the major to v1 just to be 100% sure nothing breaks.

We're testing the change internally in our fork and looks like the insights SDK is behaving slightly differently, we had to disable it during tests in a more specific way than what we used to be, but it might just be flaky tests on our side.

Happy to provide more context/discuss if needed.

@fmaule since you mentioned the different behaviour with the new SDK, would it be worth it if we split this PR into 2 different features: first the URI filter and then the new functionality offered by the new version? That would tackle one of your main concerns about the manifest metrics (and would also enable its usage in other services that don't require the new Azure features, like ours) and give you more time to investigate the differences.

[fmaule]

@neodmy that makes sense.

I am sorry but given this took too long to get merged, I've added changes on our fork also to really disable azure-metrics when using it as a systemic component.

That removes completely any issues during tests and also avoids unwanted network requests.
I might raise a new PR here at a later stage, pulling from our fork. For now, we can probably just trash this PR, or you can use any part of it, if needed.

Thanks, anyway