feat: detect unprocessable packages

[iliapolo]

Based on our experience from construct hub, adding a few surgical error handling:

Uninstallable Packages

Some packages cannot be installed. We've observed the following:

• No spec declared in a package.json dependency. For example: https://github.com/markusl/cdk-codepipeline-bitbucket-build-result-reporter/blob/v0.0.7/package.json#L35.
• Dependency conflict caused by a fixed peerDependency. For example: https://github.com/opencdk8s/cdk8s-mongo-sts/blob/v0.0.7/package.json#L60

Corrupt Assembly

Some packages have a corrupt assembly. We've observed the following:

• Packages suspcestable to fix(jsii): incorrectly allowed unexported type in constructor params aws/jsii#3147. For example: @epilot/cdk-constructs@1.0.7
• Packages who's peerDependency underwent a breaking change in a minor version. For example @pahud/cdktf-aws-eks@0.0.14

Unsupported Language

Added this detection here to further alleviate burden from callers.

[Chriscbr]

I wonder if it would make sense to vend the packages in these tests as fixtures instead?

[iliapolo]

Possibly. I don't think it makes that much of a difference since dependencies are still fetched from NPM.

The right thing to do here is to create a fixture project that simulates the scenario under test...but...for another time :)