Module supports wildcarded paths but prevents them in form validation

Problem
Whilst the module supports upon loading paths the concept of matching those with wildcard (asterisk) the submission validation for the path edit form results in the ability to save paths with aforementioned wildcards. As such if I wanted to use the path news/*, this cannot currently be achieved.

Solution
The validation should be adapted for paths that contain a wildcard, as they will neither be a valid URL (when checked with drupal_valid_path) nor will they match a source (as per drupal_lookup_path). One such aproach might be to allow the validation to be bypassed in a situation where the URL is not external, but also contains a wildcard.