Refactor registration to artifact operation

[wiktork]

Summary

Addresses #3916.

Release Notes Entry

Fixes issue where trace operations with an egress provider and rundown on Linux would cause dotnet-monitor to lose connectivity with the target application.

[schmittjoseph]

Since this is a bug fix, mind adding the update-release-notes tag and a Release Notes Entry in the PR description?

[jander-msft]

FYI, this has each of the operations register themselves with the tracker regardless of listen vs connect mode, but I think that should be fine.

[wiktork]

FYI, this has each of the operations register themselves with the tracker regardless of listen vs connect mode, but I think that should be fine.

That's a good point, but I'm actually going to leave this for now. If we bridge more of the capabilities between connect and reverse modes, this may end up being useful.

[wiktork]

/backport to main

[github-actions]

Started backporting to main: https://github.com/dotnet/dotnet-monitor/actions/runs/4430583897

[schmittjoseph]

/backport to release/7.1

[github-actions]

Started backporting to release/7.1: https://github.com/dotnet/dotnet-monitor/actions/runs/4578084019

[github-actions]

@schmittjoseph an error occurred while backporting to release/7.1, please check the run log for details!

Validation Failed: {"resource":"PullRequest","code":"custom","message":"No commits between release/7.1 and backport/pr-3960-to-release/7.1"}