Registry-published nodes show blank stars / last-updated on Manager card

## Summary

Nodes published exclusively via the Comfy Registry show blank star count and "last updated" date on their Manager card, even though the `Repository` URL is correctly declared in `pyproject.toml` and the node installs without issue.

## Reproduction

1. Publish a node using `comfy node publish` (or the GitHub Actions publish workflow) with a valid `pyproject.toml` including `[project.urls] Repository = "https://github.com//"`.
2. Open ComfyUI-Manager → Install Custom Nodes and find the node.
3. The install button and description populate correctly, but **star count and last-updated date are blank**.

Example: [`EA_LMStudio`](https://github.com/EnragedAntelope/EA_LMStudio) — published to the Registry, `pyproject.toml` parses cleanly, but card shows no stars or date.

## Suspected cause

Based on reading the Manager codebase, star count and last-updated appear to come from `github-stats.json`, which is populated by a scraper that walks `custom-node-list.json`. Publishing to the Registry does not feed this pipeline at all, so registry-only nodes never get a `github-stats.json` entry, and those two fields stay blank.

The workaround is to also open a PR adding the repo to `custom-node-list.json` — but that's the legacy manual-curation path the Registry was meant to replace.

(I'm describing the suspected mechanism, not asserting it as ground truth — happy to be corrected if the data path is different in the current v4 Manager.)

## Why this matters

Comfy-Org's own Registry launch post framed the manual `custom-node-list.json` PR process as the unsustainable prior approach, with the Registry as the replacement. Asking registry publishers to *also* PR into the legacy list — just to populate two cosmetic fields — is friction that directly contradicts that stated direction. This affects every node that went registry-only rather than dual-listing.

## Suggested fix

The Registry already stores the `Repository` URL from `pyproject.toml`. The cleanest fix is for the Manager (or the Registry backend) to derive stars and last-commit directly from that stored URL, so the card is complete after a single `comfy node publish` with no additional steps. This aligns with the migration trajectory rather than fighting it.

A smaller alternative: have the registry-backend or a CI job populate `github-stats.json` entries for registry-listed repos automatically, without requiring a manual `custom-node-list.json` PR.

## Environment

- ComfyUI-Manager (current main)
- Node published via Comfy Registry with valid `pyproject.toml`