Some Service Connector flags are unexpected given context

### Describe the bug

I found this experience to be a little odd/unexpected:

```bash
# this was a little strange, name is ambiguous
# I would expect --name to be the name of the connection (or that would be an arg, not a flag) as --connection implies a different thing (rather than "this" thing to show). --name seems like it ought be "this" thing to show, which would be implied context. If it was --cluster-name, then it would be a clear different context
az aks connection show --connection --resource-group --name
```
I would find this more clear:
```bash
# for clarity, this would clarify ux:
az aks connection show --resource-group --cluster
# or alternatively
az aks connection show --name --resource-group --cluster
```

### Related command

`az aks connection`

### Errors

No error, this is a UX related bug.

### Issue script & Debug output

No script needed.

### Expected behavior

Clarification of resources given flags provided.

### Environment Summary

az version
{
"azure-cli": "2.65.0",
"azure-cli-core": "2.65.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"interactive": "1.0.0b1",
"scenario-guide": "0.1.1"
}
}

### Additional context

_No response_