Add language detection to auto-monitor to inject only the relevant SDK

[Miqueasher]

Summary

When monitorAllServices: true, auto-monitor currently injects all 4 language SDK init containers (Java, Python, Node.js, .NET) into every pod regardless of runtime, causing liveness/readiness probe failures, restart loops, and deployment instability.

This PR adds a registry-based language detector that inspects container image config (ENV, CMD, ENTRYPOINT) via google/go-containerregistry without pulling layers (~100-500ms, 5s timeout)
Falls back gracefully through image name patterns → pod-spec env vars → pod-spec commands → all languages (current behavior), ensuring zero regression

Detection Layers

1. Registry image config — fetch ENV/CMD/ENTRYPOINT from manifest (public registries + ECR with IRSA)
2. Image name patterns — match language keywords in image reference
3. Pod-spec env vars — check for JAVA_HOME, PYTHONPATH, NODE_ENV, DOTNET_ROOT, etc.
4. Pod-spec commands — match runtime binaries (java, python, node, dotnet)
5. Fallback — all configured languages

Dependencies added

Package | Version | Purpose
github.com/google/go-containerregistry | v0.20.0 | Fetch image config from registry without pulling layers
github.com/aws/aws-sdk-go (existing) | v1.45.25 | ECR auth via custom keychain

Test Plan

• Unit tests: 92/92 passing (65 new + 27 existing, zero regressions)
• Live EKS validation (us-east-1): Custom operator build deployed with monitorAllServices=true, no manual annotations
• Java, Python, Node.js, .NET public images → 1 init container each (detected via registry config)
• Alpine, Nginx, Busybox → 4 init containers (correct fallback, no false positives)
• Private ECR image with language keyword → detected via image name pattern
• Pod-spec JAVA_HOME on Alpine → detected via env var fallback
• Multi-container (Python + Nginx sidecar) → correctly detected Python only
• Failure mode: When all detection fails, behavior is identical to current production
• Operator image digest confirmed matching between running pod and ECR (sha256:5f74a89f76b3...), zero pod restarts observed

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[mxiamxia]

The new revision looks good to me. Pls resolve the conflicts and I'll approve CR from my side.

[v-iw]

Hi @Miqueasher — this PR has conflicts with main and I don't have permissions to push to your fork, so I've rebased your commits onto current main and opened #409 to carry it forward. Your two commits are preserved as-is with you as the author.

The three source files in #409 are byte-identical to this PR at acf4dc8. The only thing I dropped is the go.mod / go.sum change: it bumped opencontainers/image-spec to v1.1.0-rc3, which was left over from the registry-inspection approach that your second commit ("removing network call") already removed. main is now on v1.1.1 and nothing in the final code imports go-containerregistry, so it was both unused and a downgrade — and it was the entire source of the conflict.

Could you take a look at #409 and confirm the rebase didn't drop anything you intended to keep? Happy to close this one out once you've verified.