add support for @clientOption("includeRootSlash")

[jorgerangel-msft]

Some legacy services require routes to not be prefixed with the / character. In example an operation with @route("?restype=container") should yield the following request uri: https://myuri/test-container-d1401e73-0567-7e68-91e8-2105f4d5001b?restype=container instead of https://myuri/test-container-d1401e73-0567-7e68-91e8-2105f4d5001b/?restype=container. The / is added by default by typespec to all routes.

We should add a new clientOption to override this behavior. When enabled, it will strip the / character from any prefixed path string.

Example usage on a client:

@@clientOption(Storage.Blob, "includeRootSlash", false, "csharp");

Example usage on an operation:

@@clientOption(Storage.Blob.foo, "includeRootSlash", false, "csharp");

Support for this option should be added for clients, sub-clients / interfaces, and operations. Sub-clients + operations should be able to override the option set by their parent.

[timotheeguerin]

can we clarify here a little bit more the issue, typespec shouldn't be adding a trailing / to any route. And if it was it definitely not a client issue that the client emitter should find a hack around, this means everything is broken

[jorgerangel-msft]

@timotheeguerin This is in support of the migration of storage to typespec. The library test recordings don't have endpoints suffixed with /. As an example, what our emitter is receiving either from tcgc or tsp for this route is:

which is causing tests to be re-recorded and we are avoiding that for this migration