fix(install): resolve '+' version in env.jsonc for env capsules

[davidfirst]

When generating .bit_roots package.json for env capsules during installation, the + version placeholder from env.jsonc was being passed directly to pnpm, causing "isn't supported by any available resolver" errors.

This affected bit lane import --pattern and bit sign when the env uses + for peer dependency versions.

Root cause: _getEnvDependencies() reads from selfPolicy (raw env.jsonc values) and passes them directly without resolving + placeholders. Previous fixes (#9641, #10037) resolved + during dependency detection and manifest building, but this code path for env capsule generation was not covered.

Fix: Pass workspaceDeps to _getEnvDependencies() and use it to resolve + version placeholders, following the same pattern as WorkspaceManifest._resolvePlusVersions.

[Copilot]

Pull request overview

This pull request fixes a bug where the '+' version placeholder from env.jsonc was being passed directly to pnpm during env capsule generation, causing "isn't supported by any available resolver" errors. This affected bit lane import --pattern and bit sign commands.

Changes:

• Modified _getEnvDependencies() to resolve '+' versions by looking up already-resolved dependencies from the env component
• Enhanced _getDefaultPeerDependencies() to use snapToSemver for converting hash versions to valid semver format
• Added comprehensive E2E test case to verify '+' version resolution during lane import operations

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
scopes/workspace/install/install.main.runtime.ts	Added logic to resolve '+' version placeholders by fetching the env component and looking up resolved versions from its dependencies, with fallback to '*'
scopes/dependencies/dependency-resolver/manifest/workspace-manifest-factory.ts	Added snapToSemver call to properly convert hash-based versions to semver format when resolving '+' placeholders
e2e/harmony/lanes/lane-import.e2e.ts	Added E2E test that creates an env with '+' version for peer dependency, then imports a lane to verify the version is properly resolved

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[davidfirst]

Addressed Copilot review comments:

1. Test comment (line 349): Applied the suggestion - changed 'workspace/bitmap' to 'workspace dependencies'.

2. install.main.runtime.ts (lines 965-971): The approach was intentionally changed after discovering that using getDependencies(envComponent) had unintended side effects - it imports the env component into the scope, causing test failures (components-index test expected 1 component but found 2). The current approach using workspaceDeps follows the same pattern as WorkspaceManifest._resolvePlusVersions and avoids these side effects. Updated the PR description accordingly.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The comment could be more specific about what workspaceDeps contains. Consider clarifying that workspaceDeps contains workspace protocol references (e.g., 'workspace:*' for pnpm) rather than actual semver versions. This helps future maintainers understand why we're using it directly instead of looking up component versions.