Add support for URL wildcards and exact URL

[varjolintu]

Adds support for URL wildcards and exact URL if the address is wrapped insinde " e.g. "https://example.com/page.php". Without wildcards, URL's are handled normally with the old/current implementation.

This feature is restricted to Additional URLs only, because storing URLs in wildcard form is not recommended, and it breaks the possibility to open the URL to a browser.

The wildcards can be used freely, and some example addresses are:

• https://*.example.com/page/*
• https://192.*.168.1/
• subdomain.of.*.example.com/page/*/login

Fixes #3718.

Testing strategy

Manually, and added automatic tests.

Type of change

• ✅ New feature (change that adds functionality)

[varjolintu]

TODO: Check if using https://doc.qt.io/qt-6/qregularexpression.html#wildcardToRegularExpression is preferred after Qt6 upgrade. Qt5 does not support https://doc.qt.io/qt-6/qregularexpression.html#WildcardConversionOption-enum.

[droidmonkey]

Oh nice that will likely replace one of our tools functions.

[droidmonkey]

@varjolintu can you rebase this onto develop?

Also want to make the change that wildcards are only valid in the "extra urls" and not the main url so click to open will still work.

[varjolintu]

@varjolintu can you rebase this onto develop?

Also want to make the change that wildcards are only valid in the "extra urls" and not the main url so click to open will still work.

This change would be very welcome. I was also concerned about this if wildcards are used in the main URLs.

[varjolintu]

Made the necessary changes. Wildcards and exact URL is now only supported in the Additional URLs section.
UrlTools::isValidUrl() needed some extra handling for the loose comparison.

[droidmonkey]

@varjolintu do you think this is ready for 2.7.10?

[varjolintu]

@varjolintu do you think this is ready for 2.7.10?

I think so. Only thing I was wondering is that should we prevent Additional URLs that are just * or *.com etc. But then again, it's up to the user what to use.

[droidmonkey]

I do believe there should at least be a root host and TLD, otherwise you are opening this feature up to phishing attacks. We can allow it but show the "red not valid" background color. Nothing really prevents the user from entering a broken url.