feat: Add Prometheus metrics for Kotary configuration parameters

[slim-d]

📊 Add Prometheus metrics for Kotary configuration monitoring

What

This MR introduces new Prometheus metrics to expose key configuration parameters from the kotary-config ConfigMap, enabling better observability and monitoring of Kotary's operational limits.

Why

• Improve observability of Kotary configuration in production environments
• Enable monitoring and alerting on configuration changes
• Facilitate troubleshooting and capacity planning through metrics visibility

Changes

Added 6 new Prometheus gauge metrics:

• kotary_max_jobs_batch_limit_ns - Maximum jobs per namespace
• kotary_max_jobs_batch_limit_cluster - Maximum jobs across cluster
• kotary_ratio_max_allocation_cpu - CPU allocation ratio per namespace
• kotary_ratio_max_allocation_memory - Memory allocation ratio per namespace
• kotary_ratio_over_commit_cpu - CPU over-commit ratio
• kotary_ratio_over_commit_memory - Memory over-commit ratio

Testing

• Metrics are properly exposed on /metrics endpoint
• Values reflect current ConfigMap configuration
• Metrics update when ConfigMap changes

Next Steps

• Update the resourceQuota dashboard to integrate these new configuration metrics alongside existing usage metrics for comprehensive monitoring

[coveralls]

Pull Request Test Coverage Report for Build 23290168111

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+6.7%) to 67.576%

---

Totals
Change from base Build 21869251553:	6.7%
Covered Lines:	446
Relevant Lines:	660

---

💛 - Coveralls