Fixing id encoding issues when using special characters for custome already on ComputeGateway

[FabianMeiswinkel]

Packages impacted by this PR

@azure/cosmos

Issues associated with this PR

ICM#315831633

Describe the problem that is addressed by this PR

PR #22548 - #22548 changed the encoding of special characters in the documentId to make sure it work with RoutingGateway - it turned out that ComputeGateway and RoutingGateway expect different encoding (RoutingGateway expects id in the Uri to be double-percent-encoded - while Compute expects it to be only single percent-encoded. Aftersome discussion we decided that ComputeGateway behavior is actually correct - and making sure SDK works weel even when id has special characters in ComputeGateway means there are no regressions for customers on RoutingGateway (same failures as before #22548) - but at least it allows us to unblock customers who want to use special characters in id by moving them from RoutingGateway to ComputeGateway. The automatic migration from RoutingGateway to ComputeGateway will also accelerate - and over time the issues in RoutingGateway will vanish.

This PR moves back to a behavior working well with ComuteGateway - and ass tests against RountingGateway and ComputeGateway in the emulator.

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

n/a

Are there test cases added in this PR? (If not, why?)

yes

Provide a list of related PRs (if any)

22548

Command used to generate this PR:**(Applicable only to SDK release request PRs)

n/a

Checklists

• Added impacted package name to the issue description
• Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
• Added a changelog (if necessary)

[sajeetharan]

LGTM!