[Record and Playback] Optimizations on new recordings

[sadasant]

When small changes happen in the tests, they generate snapshots that might not be necessary to add as changes to the repository, since they only consist on minor variations that are irrelevant to the tests, such as a date change or the value of a temporary token. See the screenshot below:

We could make the recorder automatically remove these values, and thus making that future test changes only show the relevant changes in the recordings and not all of these minor & irrelevant differences.

Recommended way to approach this:

• Look for previous PRs that have changed recordings. Some examples:
  • StorageBlob recordings history: https://github.com/Azure/azure-sdk-for-js/commits/master/sdk/storage/storage-blob/recordings
  • KeyVault Keys recordings history: https://github.com/Azure/azure-sdk-for-js/commits/master/sdk/keyvault/keyvault-keys/recordings
• From those changes, find common patterns that could be removed from the recordings automatically, then make a list or table with all of them and a note of how to replace them.
• Review the list of patterns with your peers.
• Make one or more PRs fixing these patterns on the recorder itself.
• Make a single PR with all the relevant recording updates, for all the relevant projects.

[github-actions]

Hi @sadasant, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.