Add extension methods to retrieve specific operation details

[OskarKlintrot]

Fix Issue #1350 .

Changes

Added the methods suggested in #1350.

Checklist

• I ran Unit Tests locally (that I added, a lot is failing locally in main on my machine).
• CHANGELOG.md updated with one line description of the fix, and a link to the original issue if available.

For significant contributions please make sure you have completed the following items:

• Design discussion issue #
• Changes in public surface reviewed

The PR will trigger build, unit tests, and functional tests automatically. Please follow these instructions to build and test locally.

Notes for authors:

• FxCop and other analyzers will fail the build. To see these errors yourself, compile localy using the Release configuration.

Notes for reviewers:

• We support comment build triggers
  • /AzurePipelines run will queue all builds
  • /AzurePipelines run <pipeline-name> will queue a specific build

[OskarKlintrot]

Does it still make sense to have OperationDetailConstants public? I noticed it haven't shipped yet. I would assume you would prefer to have a small public surface?

I noticed the request detail can be HttpWebRequest and the response detail can be HttpWebResponse so I guess they can be left public.

[TimothyMothra]

LGTM