[Agents Extension] Update show and monitor commands to not require parameters

[trangevi]

Other commands rely on the azd service entry to get name/version/etc. details. This PR brings show and monitor in line with the rest

[Copilot]

Pull request overview

Updates the Azure AI Agents extension show and monitor commands to resolve agent name/version from the azure.yaml service configuration and current azd environment, making these commands consistent with other extension commands and removing the need for explicit --name/--version parameters.

Changes:

• Update show and monitor to accept an optional positional [service] argument and resolve agent details via azd project/environment APIs.
• Remove required --name/--version flags (and related account/project flags) from both commands and refresh help/examples accordingly.
• Adjust unit tests to reflect the new positional-arg behavior and removed required flags.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
cli/azd/extensions/azure.ai.agents/internal/cmd/show.go	Switch show to [service] positional arg and resolve agent name/version from azd project + environment.
cli/azd/extensions/azure.ai.agents/internal/cmd/show_test.go	Update tests to validate new arg behavior and removal of required flags.
cli/azd/extensions/azure.ai.agents/internal/cmd/monitor.go	Switch monitor to [service] positional arg and resolve agent name/version from azd project + environment; adjust session resolution call site.
cli/azd/extensions/azure.ai.agents/internal/cmd/monitor_test.go	Update tests to validate new arg behavior and removal of required flags.

Comments suppressed due to low confidence (1)

cli/azd/extensions/azure.ai.agents/internal/cmd/monitor.go:121

• newMonitorCommand creates an AzdClient (azdext.NewAzdClient) and later resolveMonitorSession() creates a second AzdClient internally. Since monitor now always needs an AzdClient to resolve the service, consider passing the existing client into resolveMonitorSession (or refactoring resolveMonitorSession to accept the already-loaded env/config path) to avoid redundant gRPC connection setup on every run.

			// When vnext is enabled, resolve session ID for session-based logstream.
			if flags.sessionID == "" {
				sessionID, vnext := resolveMonitorSession(ctx, info.AgentName)
				if vnext {
					if sessionID == "" {
						return exterrors.Validation(
							exterrors.CodeInvalidSessionId,
							"VNext agents are currently enabled and require a session ID for log streaming.",
							"Specify the session ID using --session, or run `azd ai agent invoke` first to create one",
						)
					}
					flags.sessionID = sessionID
				}

---

You can also share your feedback on Copilot code review. Take the survey.