Change how required parameters are represented in URI Templates

[darrelmiller]

Currently all parameters are rendered in URI templates like this:

  {+baseUrl}{?paramA,paramB,paramC}

I would like us to consider changing the way required parameters are presenting. Consider paramA and paramB are optional, but paramC is required, the URI Template would be

  {+baseUrl}?paramC={paramC}{&paramA,paramB}

With this approach, query parameters that are required but allow an empty value, do not require the application developer to explicitly set the empty value.
The other advantage is that when using this URI Template for documentation/debugging purposes it is very clear which parameters are required vs optional.
This approach also produces a more stable URL as the order of query parameters is impacted less due to the presence of optional parameters. This is helpful to prevent HTTP cache pollution.

[baywet]

related microsoft/kiota-dotnet#172

[baywet]

@sebastienlevert for prioritization

[sebastienlevert]

This seems like a clear bug and impact current customers. I'll add it to our 1.11 release.