feat: Add microcks health command for server connectivity diagnostics

[kunal-yelgate]

Current Behavior

No dedicated command to check Microcks server health. Users infer status from cryptic errors during import/test commands. Reduce debugging time and enable proactive health monitoring in production environments.

Why we need this?

• No quick way to verify server health before imports/tests
• Debugging connection issues wastes developer time
• No CI/CD pre-flight health check support

How will this help?

• microcks health gives instant server diagnostics
• --watch enables continuous monitoring during deployments
• --json supports CI/CD pipeline integration
• Exit codes (0/1/2) enable automation

This error could mean:

• Microcks server is not running
• Wrong port or hostname
• Network firewall blocking connection
• Server is starting up but not ready yet
• TLS certificate issue

Debugging requires manually using curl or checking Docker logs.

Desired Behavior

Add microcks health command for quick server diagnostics:

$ microcks health
Microcks Server Health Check
============================
Server URL: http://localhost:8585/api

✓ Reachable (HTTP 200, 45ms)
✓ API endpoint responding
✓ Keycloak: enabled and reachable
✓ Async Minion: connected
✓ Database: connected
✓ Version: 1.14.0 (stable)

Overall Status: HEALTHY ✅

[github-actions]

👋 @kunal-yelgate

Welcome to the Microcks community! 💖

Thanks and congrats 🎉 for opening your first issue here! Be sure to follow the issue template or please update it accordingly.

📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌"

Hope you have a great time there!

🌟 ~~~~~~~~~ 🌟

📢 If you like Microcks, please ⭐ star ⭐ our repo to support it!

🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️