Gradle nested subproject with number in name

[plannigan]

How are you running Renovate?

A Mend.io-hosted app

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

Reproducible Repo
Hosted Job Number: 01944d59-170f-727b-bfd0-2e2561092ae5

When a Gradle project has a subproject that is nested within multiple directories AND has a digit in the project name, Renovate considers the included() line within settings.gradle.kts as a dependency specification. As a result, the execution raises a warning about not being able to find the package.

Logs (if relevant)

Logs

...
packageFiles with updates
{
  "baseBranch": "main"
  "config": {
    "gradle": [
      {
        "packageFile": "settings.gradle.kts",
        "datasource": "maven",
        "deps": [
          {
            "depName": "libs:foo",
            "currentValue": "some-e2e-lib",
            "managerData": {
              "fileReplacePosition": 93,
              "packageFile": "settings.gradle.kts"
            },
            "fileReplacePosition": 93,
            "datasource": "maven",
            "registryUrls": [
              "https://repo.maven.apache.org/maven2"
            ],
            "depType": "dependencies",
            "updates": [],
            "packageName": "libs:foo",
            "versioning": "gradle",
            "warnings": [
              {
                "topic": "libs:foo",
                "message": "Failed to look up maven package libs:foo"
              }
            ]
          }
        ]
      },
...

[rarkins]

What logic could Renovate use to know that this is not a dependency to look up?