Fix URL parsing issues

[GeekJosh]

I recently had an issue connecting my Roku device to my Jellyfin server as my server is setup to expect certain query string values in the URL. When I looked into the code, I found that this was due to the URL parsing logic during server selection not accounting for the presence of a query string and appending the API path to the end of the URL, making it invalid.

Changes

• update the logic in misc.inferServerUrl, misc.urlCandidates and baserequest.buildURL to properly handle query string values present in the given URL
• fix an issue in baserequest.buildURL when certain functions include the query params in path rather than params
• replace misc.parseUrl with new ParsedUrl function (defined in parsedUrl.bs), which returns an associative array of URI components parsed from the given URL and defines helper functions for manipulating it safely

Issues

#601

[1hitsong]

Functionality seems to work to me 🤘🏻. Code style changes requested.

[1hitsong]

One more style pass. Everything else is looking good to me.

Do you want your name in the What's New content popup? If so, add an entry to the source\static\whatsNew\3.0.13.json file.

I'd suggest the description be something like "Add support for querystring values in server address"

[GeekJosh]

thanks for persevering @1hitsong - I've applied your suggestions and updated "what's new" now

[1hitsong]

Nice job.