Fallback to concatenating strings when a IIIF image URL contains a query parameter

https://redmine.teklia.com/issues/9411

Importing this manifest fails because from an image ID of https://bibnum.institutdefrance.fr/i/?IIIF=/a6/a6/b8/57/a6a6b857-403d-4054-9f90-399035760e03/iiif/T0000002.tif, the file import uses the information URL https://bibnum.institutdefrance.fr/i/info.json. Unfortunately, most IIIF implementations only concatenate strings and do not use an equivalent of urljoin to build URLs, so they have set a new standard where everyone expects every IIIF implementation to work even with unexpected query parameters.

Just like what was done in arkindex/backend!2309 (merged), the IIIF import should fallback to concatenating strings to build URLs instead of urljoin, but only when we detect that there are query parameters set on the URL.