[Feature]: Load provider logos from their own repositories #1623

Before submitting

• I searched existing feature requests and discussions for provider icons and found no matching request.

Problem or motivation

I built a Harvester provider and have it working with Devsy Desktop and devcontainers in my homelab. I'd like it to show the official Harvester logo when I add it.

In v1.24.0, ProviderConfig already defines icon and iconDark, but Desktop's ProviderIcon component takes the provider name and selects from a fixed map. Harvester falls through to the placeholder. Adding a logo to our provider manifest therefore wouldn't make Desktop use it.

Proposed solution

Let the provider repository own its logo, and have Desktop load it from there when the provider is added or updated.

For example, our repository could contain assets/harvester.svg and reference it from the provider manifest. Desktop could resolve that path against the provider source/version being installed. The same idea could support a dark-mode image through iconDark.

The exact convention is up to you. A manifest-relative image path would make the relationship explicit; an agreed default logo filename could also work. The main thing is that adding or updating a provider's logo should be handled in that provider's repository, without adding an asset/map entry to Devsy and waiting for a Desktop release. Existing absolute image URLs could remain supported too.

Keep the current mapping and placeholder as fallbacks when a provider has no logo or its image can't be loaded.

Alternatives considered

Add a Harvester asset and map entry directly in Desktop, like the Lima/OrbStack change. That works for individual providers, but loading the image from the provider repository seems more useful generally.

Area

Desktop app, Providers

Acceptance criteria

• A logo checked into a custom provider's repository appears in the provider list and setup flow without a Devsy source change.
• Repository-relative image references resolve against the provider source/version being installed.
• A configured dark-mode image is used when available.
• Providers without custom icons retain the existing mapping/placeholder behavior.
• A failed logo request falls back without breaking provider setup.