fix(operator): warn when VirtualMCPServer inline telemetry is ignored

[RaviTharuma]

Follow-up from #6276 after closing #6277. Operator ignores spec.config.telemetry and emits a one-shot Warning (InlineTelemetryIgnored) when it is set without telemetryConfigRef. Docs no longer claim inline still works for operator vMCP. /metrics stays unregistered without the ref (HTTP 406).

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[codecov]

Codecov Report

❌ Patch coverage is 36.36364% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 77.74%. Comparing base (b48013e) to head (43c6b0a).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...perator/controllers/virtualmcpserver_controller.go	22.22%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6408      +/-   ##
==========================================
+ Coverage   77.69%   77.74%   +0.05%     
==========================================
  Files         752      756       +4     
  Lines       72717    72799      +82     
==========================================
+ Hits        56500    56601     +101     
+ Misses      16212    16193      -19     
  Partials        5        5              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[blkt]

nit: this is passing both vmcp and a boolean calculated on its fields. Is there a reason why vmcp.Spec.Config.Telemetry and vmcp.Spec.TelemetryConfigRef are evaluated outside? If not, would you mind reducing this to func emitInlineTelemetryIgnoredEvent(vmcp *mcpv1beta1.VirtualMCPServer) and do al the math in it?