Enable full dependency resolution in AddDependencyExecutor

[aem]

What do you want and why?

Currently the AddDependencyExecutor just blindly installs the version specified in the executor's metadata, which isn't exactly what we want - we want a pinned version.

Possible implementation(s)

We should use the same dependency resolution logic we use in the blitz new command to resolve the latest valid version for each dependency based on the version string passed in (that may require pulling that logic out into a utility package for sharing, or just copy/pasting it.

[merelinguist]

it’s because the published version of the installer doesn’t try to install ts-node if it’s not already registered, which it is when yarn linked

Waiting on refactor

[aem]

@merelinguist finished that refactor, should be good to go now

[merelinguist]

@aem Thanks for the heads up :)