OPT: Support list query parameters

[JeroennC]

Before this change it would URL encode the python representation of the list.
With this change it will pass the query parameter as ?multivalue=value1&multivalue=value2

I was doubting whether to use isinstance(.., list) vs something more generic like isinstance(.., Collection), but i believe list is the most appropriate typing. It has order, and it clearly defines what would be expected when passing a list as a query parameter.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.43%. Comparing base (e4aabd0) to head (062356d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #133      +/-   ##
==========================================
+ Coverage   92.39%   92.43%   +0.03%     
==========================================
  Files          33       33              
  Lines         855      859       +4     
  Branches      129      131       +2     
==========================================
+ Hits          790      794       +4     
  Misses         45       45              
  Partials       20       20              

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

[eigenein]

I'd actually prefer to accept any iterable here (say, a tuple). The docs say the most reliable way would be:

try:
    values = iter(value)
except TypeError:
    ...  # old code for scalar values
else:
    for sub_value in values:
        ...

[JeroennC]

Yeah i thought about accepting any iterable, however that would also cover strings which we don't want to iter through here.

[eigenein]

Oh, good one, didn't think of strings. They'd also pass isinstance(..., Collection) check

[eigenein]

Also, please don't care fixing the 3.8 checks – it's end-of-life, I'll remove the support completely