include_external_repositories needs trailing wildcard to match bzlmod-created repo

In https://github.com/bazel-contrib/bazel-lib/pull/1071/commits/5fee53342b94195f95a5bbabd82c09317454d921 I moved a test fixture from WORKSPACE to MODULE.bazel, and was forced to add a `?` wildcard to match `+` or `~` due to apparent vs. canonical repository naming. This indicates the feature has never worked properly for bzlmod external repositories.