Rework `forSubgraph` as implied by `strictly` This commit removes a dedicated `forSubgraph` flag on version constraints, so that it is _implied_ by strict version constraints. This simplifies the behavior of `strictly`, making it closer to the intuitive semantics, while maintaining the ability to fail the build if a consumer brings an incompatible version in the graph.
As a consequence, _strict dependencies_ now express that the producer preference overrides whatever is found in its own dependency graph. It is closer to the "nearest first" semantics of Maven, while not having its drawbacks (ordering in particular).
Remove brittle check for failure type The difference between `FAILED` and `REJECTED` is not apparent from the error message, and is unimportant for this test. This difference is still validated by the equivalent unit test.