Config migration adds a potentially redundant "{/,}" suffix when migrating matchPackagePrefixes to matchPackageNames

[Egorand]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Our project uses Renovate to manage Gradle packages, and most artifacts are declared using the "group:artifact:version" notation. Our renovate.json5 config file contained a bunch of package rules that used matchPackagePrefixes to match packages. Renovate recently opened a PR migrating our config to use matchPackageNames instead (as it seems that matchPackagePrefixes was removed), and migrations looked roughly like this:

- matchPackagePrefixes: [
+ matchPackageNames: [
-   'de.undercouch:gradle-download-task',
+   'de.undercouch:gradle-download-task{/,}**',
]

If my understanding is correct, the {/,} portion of the pattern matches an optional / character. However, Gradle package names don't usually include the / character (in fact, I'm not even sure if it's an allowed character), therefore that suffix is redundant in our case. Is it possible that this suffix (introduced in #30394) targets a specific type of packages?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks