[Feature Request] Support for Consul tags

[SCcagg5]

Description

Feature Request: Consul Service Discovery Provider

Summary
Add native Consul service discovery support to Homepage, similar to existing Docker/Kubernetes providers.

Why
Consul is often the source of truth for service discovery and health checks (Nomad, Docker, VMs, service-mesh).
Today, integrating Homepage with Consul requires custom bridges or YAML generation.

What

• Read services from Consul HTTP API
• Map Consul tags to Homepage fields (homepage.*)
• Use Consul health checks for service status

Example config

providers:
  consul:
    url: http://consul:8500
    token: ${CONSUL_HTTP_TOKEN}

Benefits

• No Docker socket required
• Better health semantics (passing / warning / critical)
• Works in Nomad & service-mesh setups

TL;DR

Homepage should be able to read directly from Consul as a first-class provider.

Other

No response