[Unified Recorder] Work on the No-op AAD credential for playback - to be in sync with .NET and Python

[HarshaNalluru]

If the AAD credentials don't take the recorder httpClient option, the AAD traffic won't be recorded.
In this case, you'll need to bypass the AAD requests with no-op in playback(since there are no recorded requests to match).
This PR provides the No-op AAD credential for playback.

The current plan is to provide both ways of recording the tests

• NoOp credential [App Config] Migrate the tests to use the new unified recorder #18896 - where the services/SDKs don't care about the AAD traffic
  • .NET and Python follows this model for all their services/SDKs
• RecorderHttpClient for AAD - Harshan/unified recorder/migrate app config #18898 - for the Services/SDKs that would want to see the AAD traffic in their tests
  • We had seen some value in recording the AAD traffic with the old recorder(in JS).
  • This has particularly helped us uncover multiple bugs in the token refreshing space where we regressed and started making more requests than expected.
  • Also helped us see how the msal has been changing over time w.r.t its request bodies.
  • We are waiting for a special kind of matcher from the proxy tool side to complete the missing pieces in this area.
  • This is exclusive for JS.