fix: wildcard pattern matching

[hvitoi]

Closes #7181

Rationale

The new URL keyword was previously instantiating an unknown class which does encode the hostname characters so that https://*.myhost.com/ was turned into https://%2A.myhost.com and the latter would not match with the actual url being requested and thus the certificate would not be attached to the request itself.

This fix forces the use of the node:url module which does return a more predictable output (and not encoding the star symbol).

It's not clear why this bug is not caught by the test suite since this exact test case is already validated. If you have any suggestion we could explore other test scenarios.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[subnetmarco]

Thanks for the contribution. @filfreire can you review it?

[hvitoi]

What are the next steps on this? @filfreire Is there any action left?

[filfreire]

@jackkav @gatzjames @CurryYangxx if possible please give a second pass to this

[jackkav]

Nice catch, can confirm. I suspect the tests pass because they run in a node context so web apis are polyfilled with node ones.