[BUG] Plugin versioning does not resolve correct version from local folder marketplaces

Follow-up to #64457

#64457 fixed plugin versioning for git-based marketplaces, but the same problem still occurs when the marketplace is added as a local folder path (that happens to be a git repo).

Problem

When a plugin declares a dependency with a pinned version (e.g. jira@ai-helpers =0.5.0), installing from a local folder marketplace installs the latest version (0.7.0) instead of the requested version (0.5.0). This causes the dependent plugin to fail to load.

Reproducer

# Clone a marketplace repo to disk
git clone git@github.com:openshift-eng/ai-helpers.git ~/git/ai-helpers

# Add a remote marketplace and the local folder marketplace
claude plugin marketplace add stbenjam/temp-marketplace
claude plugin marketplace add ~/git/ai-helpers

# Install a plugin that depends on jira@ai-helpers =0.5.0
claude plugin install bundle-test@test-marketplace

The git repository has the tags available:

$ cd ~/git/ai-helpers
$ git tag -l | grep jira--
jira--v0.5.0
jira--v0.6.0
jira--v0.7.0

Expected

jira@ai-helpers version 0.5.0 is installed to satisfy the dependency.

Actual

jira@ai-helpers version 0.7.0 (latest) is installed, and bundle-test fails to load:

❯ bundle-test@test-marketplace
  Version: 0.1.0
  Scope: user
  Status: ✘ failed to load
  Error: Requires "jira@ai-helpers" =0.5.0, installed 0.7.0

❯ jira@ai-helpers
  Version: 0.7.0
  Scope: user
  Status: ✔ enabled

Notes

• The git-based marketplace case was fixed in #64457