Add hosting.md documentation for go-micro services

[Copilot]

Addresses the question of how people host go-micro services by documenting current options and what a purpose-built platform would look like.

New doc at internal/website/docs/hosting.md covering:

• Current hosting options — Single VPS with systemd/mDNS, multi-server with Consul/Etcd, containers/Kubernetes, PaaS
• Platform requirements — Service discovery integration, RPC/messaging, config management, storage backends, health checks, security (TLS + auth), horizontal scaling
• Ideal platform architecture — ASCII diagram showing gateway → services → private network (registry, broker, store)
• Comparison matrix — Complexity, cost, scaling, discovery, and ops overhead across all four strategies
• Progressive adoption path — Start with single VPS, add registry for multi-host, containerize, then orchestrate

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Hosting</issue_title>
<issue_description>Is anyone looking for hosting? How do people host their services right now?</issue_description>

<agent_instructions>Identify what a hosting platform would look like for go micro services. Outline as a document in the docs called hosting.md</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Hosting #2847

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.