fix(installer): display declared versions for custom modules

[lorenzozanee]

What

Display the declared version for unpinned Git custom modules in installer status and generated manifests.

Why

Unpinned custom modules were reported as main even when marketplace metadata declared a version.

Fixes #2907

How

• Prefer the resolved module version after an explicit cloned ref.
• Keep main as the fallback when no version metadata is available.
• Add regression coverage for the marketplace version path.

Testing

Passed node test/test-installation-components.js (496 tests), node test/test-installer-channels.js (83 tests), changed-file Prettier and ESLint checks, and git diff --check.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge, with the fallback change matching the installer’s existing metadata-resolution semantics and focused regression coverage.

Summary

This PR corrects custom-module version reporting by preferring resolved version metadata before falling back to main for unpinned Git modules.

• Updates custom-module manifest version selection while preserving explicit clone refs as the highest priority.
• Adds regression coverage for versions declared in marketplace metadata.

_{Reviews (1) · Last reviewed commit: "fix(installer): preserve custom module v..."}