Add support for query parameters in the PathConfiguration

[leonvogt]

Currently, a PathConfiguration that captures certain URL parameters, such as:

{
  patterns: [".*\\?open_in_external_browser=true.*"],
  properties: {open_in_external_browser: true}
}

works out of the box in Turbo-Android but not in Turbo-iOS.
There is a comment in the properties implementation that says query parameters are not supported yet but likely will be in the future.
Is there a technical reason why this was not implemented yet?
Before creating a PR, I wanted ask what the reasons were for this decision and what we need to consider when implementing this feature.
It would be nice if Turbo-iOS and Turbo-Android would behave the same way in this regard.
Thanks!

[jayohms]

It would be nice if Turbo-iOS and Turbo-Android would behave the same way in this regard.

100%. There's no technical reason why they're different — except oversight. Let's align them. Since this is a potential change in behavior for existing path configuration files, we'll likely need to add a new configuration option to maintain the current behavior.

[joemasilotti]

@leonvogt, let me know if you're open to submitting a PR. If not, I'm happy to take a pass myself.

[leonvogt]

@jayohms thanks for the fast reply!
I'm not quite sure I understand your suggestion with the configuration option.
To maintain the current behavior, I would introduce an optional parameter to the properties function, that will enable the new behavior.
People who don't want the new behavior can use this parameter to opt out of this change.
I created a small PR to demonstrate this idea: #190

@joemasilotti if this PR goes in a different direction than you intended, I'm happy to close it in favor of your approach.