suggest unlocking locked pkgs that cause dep resolution failures

[raquentin]

Resolves #3622

Changes:

• expanded Error::dependency_resolution_failed to detect dependency resolution failures due to locked packages in two ways
• the first involves ResolutionError::NoSolution. These are errors where a locked package version is incompatible with a new package added via gleam add or via a manual gleam.toml update and gleam deps download AND the locked package is not constrained in manifest.toml. More manual testing is needed for the larger cli interactions. resolution_locked_version_doesnt_satisfy_requirements_indirect tests this case.
• the second is when a version in the locked map is not in the range specified in requirements. resolution_locked_version_doesnt_satisfy_requirements tests this case.
• added a new error variant DependencyResolutionFailedWithLocked to allow pattern matching later to start the CLI action (waiting for user to [y/n] the suggestion)

Questions for reviewers:

• Can you look over the wording of error messages
• Do you want to unit test the integration the new CLI dialogue? If so is there a similar example already in the codebase? Would've done it by default if I had a clearer plan for setting env vars and interacting w/ stdin
  Ty

[raquentin]

Looking for suggestions of better designs for this section. Cloning for use in calling the function recursively on the should_try_unlock page feels a bit gross

[raquentin]

A bit redundant, could remove, lmk