[Issue] Unable to use Geneva metrics connector

Issue Description
I added a metrics connector to our agent so it could view hot path metrics that are not emitted to Kusto. After I asked the agent to use the connector, it claimed there was a product / schema gap as it could not determine a way to pass in the hot path namespace to the skill. See the output below from the agent:

**No — the connector is registered, but I still can't query the metrics.** The blocker is a tool schema gap, not your configuration.

## What's working

The connector landed correctly. My configuration snapshot (regenerated 18:26 UTC) now shows 5 connectors including:

| Field | Value |
|---|---|
| name | `CloudTestHotPathMetrics` |
| dataConnectorType | `GenevaMetrics` |
| identityPresent | `true` |
| dataSourcePresent | `true` |
| extendedPropertyKeys | `monitoringAccount` |

A `Geneva` metric provider is also a supported value on the metrics tooling, so the path genuinely exists.

## What's blocking

Every call fails with the same error, before it ever reaches your account:

```
Metric namespace must be provided. (Parameter 'metricNamespace')
```

The problem is that **`metricNamespace` is a required backend parameter that isn't exposed in the tool schema I'm given.** The metric tools accept only `metricProvider`, `resourceId`, `metricName`, `resourceDetails`, times, and `aggregation` — there is no namespace field for me to populate. I tried routing `CTProdAKS` through every available channel:

- `resourceId` = `CTProdAKS`
- `resourceId` = `CloudTest/CTProdAKS`
- `resourceId` = `/accounts/CloudTest/namespaces/CTProdAKS`
- namespace prefixed onto `metricName` = `CTProdAKS/dotnet.thread_pool.queue.length`
- namespace declared inside `resourceDetails`

All five returned the identical error, which tells me the backend isn't parsing the namespace out of any of those fields — it wants a discrete `metricNamespace` argument that the schema doesn't offer. I stopped there rather than continuing to guess at formats.

Importantly, **this is not an auth or permissions failure.** I never got far enough to exercise the managed identity against the `CloudTest` account, so whether the RBAC is right is still unverified — it's simply untested.

## What would fix it

This needs a product-side change, not something you can configure around:

1. **Most likely:** the `GenevaMetrics` connector should supply `metricNamespace` from its own configuration — it already carries a `monitoringAccount` extended property, so a matching namespace property (or a namespace on the connector's data source) is the natural fix.
2. **Alternatively:** expose `metricNamespace` as a parameter on the metric tools so I can pass `CTProdAKS` explicitly.

Worth raising with the SRE Agent product team, since it likely affects any `GenevaMetrics` connector, not just yours. If there's a connector field for namespace I haven't seen — the snapshot only reports property *key names*, not values — setting it there may be all that's required, and I'm happy to re-test immediately.

Thread ID
f808bf81-5547-4004-a1d7-e910aeede1cb

Steps to Reproduce
1. Added the Geneva Metrics (MDM) connector via the SRE portal
2. Asked SRE agent to query a metric and pre-aggregate of my choosing

Expected Behavior
It should have retrieved the metric data.

Actual Behavior
It said there was a gap in the schema of the skill and the connector as there was no way to specify the namespace of the hot path metric.

No repository file or test is named. Start by locating the GenevaMetrics connector configuration and the metric tool schema, then check how the metric namespace can be supplied; the issue is done when a Geneva hot-path metric query succeeds with the namespace provided.

Written by the indexing model from the issue text.