Fail hard on failure to resolve dependencies

[timtebeek]

What's changed?

Fail hard on failure to resolve dependencies, as opposed to continuing with partial type information.

What's your motivation?

Partial type information can lead to missing changes, and hard to trouble shoot issues. We'd rather fail fast and hard, such that the underlying issues can be addressed.

Anything in particular you'd like reviewers to focus on?

Not too familiar with Gradle plugin development; throwing a GradleException seemed the best fit to achieve something similar to what we did in the Maven plugin.