Intoroduce query parameters with multiple values to Endpoint API

[ekhov]

Introduce query codec for multi value query parameters. Now HttpCodec.Query[A] returns Chunk[A] as a result value. Add new query codecs to describe these multi value parameters to QueryCodecs preserving old ones(query etc), which are now a transformed versions of multi value codecs.

Now single value codecs fail if endpoint receives multiple values for this query

/claim #2321

[jdegoes]

There is a Scala 3 build failure that is failing the build (maybe among other things).

[codecov-commenter]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (6930757) 65.38% compared to head (00bf4b9) 65.46%.

Files	Patch %	Lines
...ed/src/main/scala/zio/http/codec/QueryCodecs.scala	90.00%	1 Missing ⚠️
...scala/zio/http/codec/internal/EncoderDecoder.scala	91.66%	1 Missing ⚠️

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2631      +/-   ##
==========================================
+ Coverage   65.38%   65.46%   +0.07%     
==========================================
  Files         144      144              
  Lines        8407     8420      +13     
  Branches     1532     1494      -38     
==========================================
+ Hits         5497     5512      +15     
+ Misses       2910     2908       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[987Nabil]

@jdegoes The way this is modeled rn makes it impossible to to analyse if it is single or multi value. This might make it hard to generate docs etc. from endpoints. What do you think about adding a field queryStyle to the codec or a new annotation?
Both could also contain information about how multi values should be rendered. ?a=1&a=2 vs ?a=1,2 vs ?a=1|2 or maybe even others.
That would likely be more important for clients, to be compliant with their requirements.

[jdegoes]

@987Nabil The way this is modeled rn makes it impossible to to analyse if it is single or multi value.

How about QueryParamHint which could be QueryParamHint.Zero, QueryParamHint.One, QueryParamHint.Many, QueryParamHint.Any. Then the constructors can feed the hint in, and the documentation generation can use the hint.

Most code doesn't need to know about that, it's only really for doc or client generation.

cc @ekhov

[987Nabil]

@ekhov I think you get the idea. Try what @jdegoes suggested and adjust the idea if needed. What is important is, that we can find intend in the data.

[ekhov]

@jdegoes Do I get it correctly that you want this hint to be added as a Query parameter? And at the moment we will use only One(single value codecs) and Many(for multi value)?