Maven 4 'Invalid Collect Request: null' on projects with uninterpolated dependency versions

## Description

When testing ~966 Apache projects against Maven 4.0.0-rc-5 (via [gnodet/maven4-testing](https://github.com/gnodet/maven4-testing)), **12 projects fail with `Invalid Collect Request: null`** during dependency resolution. These projects all build successfully with Maven 3.

The error occurs when transitive dependencies in published POMs have `${...}` version expressions that Maven 4's stricter resolver cannot resolve, resulting in a null groupId/artifactId/version in the collect request.

## Affected projects

activemq-openwire, camel-quarkus, causeway-app-helloworld, causeway-app-petclinic, causeway-app-simpleapp, ctakes, incubator-streampark, logging-flume, logging-log4j-audit, mina-sshd, sling-org-apache-sling-app-cms, unomi

## Build command

```
mvn -V -B -e clean package -DskipTests
```

Maven version: 4.0.0-rc-5

## Summary issue

Full test run results: https://github.com/gnodet/maven4-testing/issues/9485

Start by reproducing the failure with Maven 4.0.0-rc-5 using `mvn -V -B -e clean package -DskipTests` against one of the listed affected projects. Review the dependency-resolution output and the full test results in gnodet/maven4-testing issue 9485; done means the affected projects no longer fail with `Invalid Collect Request: null` while Maven 3 behavior remains intact.

Written by the indexing model from the issue text.