Add support for query parameters in the PathConfiguration

[leonvogt]

closes #188

[joemasilotti]

@jayohms, this is ready for review now having moved to a global configuration, only.

I'd love your feedback on the naming of the configuration option. I nested it under a new sub-class which makes sense to me:

Turbo.config.pathConfiguration.matchQuery = true

But I'm open to keeping it one level deep and using:

Turbo.config.matchPathConfigurationQuery = true

Or something similar/cleaner.

[leonvogt]

Thanks a lot for your commits @joemasilotti!
Looks a lot better now!

One question though:
On the Android side the query parameters are beeing checked by default.
With the current implementation of this PR, they are not being checked by default. As a result, users would need to manually update the global configuration to align with the same behavior as Turbo Android.

Would you be open to the idea of enabling this feature by default to align the behavior?
I understand that it might introduce some unwanted side effects for users. However, if we declare it as a potential breaking change in the release notes, users who prefer to maintain the old behavior could simply update the newly introduced global configuration.

What are your thoughts on this?

[jayohms]

Suggested change

	Turbo.config.pathConfiguration.matchQuery = true
	Turbo.config.pathConfiguration.matchQueryStrings = true

[jayohms]

Suggested change

	if Turbo.config.pathConfiguration.matchQuery, let query = url.query {
	if Turbo.config.pathConfiguration.matchQueryStrings, let query = url.query {

[jayohms]

Suggested change

	public var matchQuery = false
	public var matchQueryStrings = false

[jayohms]

One question though:
On the Android side the query parameters are beeing checked by default.
With the current implementation of this PR, they are not being checked by default. As a result, users would need to manually update the global configuration to align with the same behavior as Turbo Android.

Would you be open to the idea of enabling this feature by default to align the behavior?
I understand that it might introduce some unwanted side effects for users. However, if we declare it as a potential breaking change in the release notes, users who prefer to maintain the old behavior could simply update the newly introduced global configuration.

What are your thoughts on this?

I'd say the only reason we're adding the new configuration option is so we avoid breaking existing apps. Otherwise, I'd be in favor of always matching patterns against path + query strings. So, let's avoid breaking apps on both platforms and keep the default behaviors in place.

We have upcoming changes later this year to make make the libraries easier to use out-of-the-box with sane defaults, so that'll be a good time to reevaluate the defaults.