[Unified Recorder] Re-enable ContinuationSanitizer tests

[timovv]

Resolves #18220

Do we need additional tests beyond this one? Let me know and I can add them.

[sadasant]

Looks good to me, but I don’t have the context regarding the new recorder. Is this enough, @HarshaNalluru ?

[HarshaNalluru]

run the test in browser too, please.

[HarshaNalluru]

The intention behind this sanitizer is to handle a case at ACR service.
Right now, the proxy tool only supports continuation sanitizer only in the headers I think.
I (vaguely) remember the ACR case to have the id at request body.

If the sanitizer can't be used for that case, it's pretty much worthless.
Can you test that case on your local, observe the changes in the recordings to understand, and then see what else we'd need to add in the proxy tool to support such a case?
@jeremymeng should be able to point you to the test case from ACR.

After you test using the ACR test, add a new test or update this test to represent the exact scenario over there.
Add more/different routes to the server under utils as needed.

[jeremymeng]

the name Continuation doesn't ring a bell. In ACR I had to sanitize part of the token value while keeping expiration info. I also had to call pluginForClientSecretCredentialTests(env.CONTAINERREGISTRY_TENANT_ID) but I don't remember the exact reason now.

azure-sdk-for-js/sdk/containerregistry/container-registry/test/utils/utils.ts

Lines 41 to 57 in c07af44

	customizationsOnRecordings: [
	(recording: string): string =>
	recording.replace(
	/"refresh_token":"[^"]+"/g,
	`"refresh_token":"sanitized.${expiryReplacement}.sanitized"`
	),
	(recording: string): string =>
	recording.replace(/access_token=(.+?)(&|")/, `access_token=access_token$2`),
	(recording: string): string =>
	recording.replace(
	/refresh_token=([^&]+?)(&|")/,
	`refresh_token=sanitized.${expiryReplacement}.sanitized$2`
	)
	],
	onLoadCallbackForPlayback: () => {
	pluginForClientSecretCredentialTests(env.CONTAINERREGISTRY_TENANT_ID);
	}

[HarshaNalluru]

@jeremymeng this is about some UUID that is present as part of the response of one request, is passed as part of a future request of the same test.

[HarshaNalluru]

Talked to Jeremy, and turns out this wasn't the requirement.
Let's move on with what we have and revisit if we need to support something else while migrating the tests.

[HarshaNalluru]

Please merge after adding the browser recording