fix: PublishCommand returns non-zero exit code on error paths

[pratapladhani]

Summary

Fixes #264 - PublishCommand now correctly returns exit code 1 on all error paths.

Problem

All ~27 error
eturn;\ paths in \PublishCommand.cs\ silently returned exit code 0 because the \SetHandler\ used a typed-parameter signature (\�sync (bool, bool, string, string?, bool) => { ... }) which returns \Task\ (not \Task). System.CommandLine always interprets this as exit code 0.

This caused calling scripts (e.g., PowerShell automation) to incorrectly report success when publish operations failed.

Fix

Switch to the \InvocationContext\ pattern (matching \ConfigCommand):

• Handler signature: \SetHandler(async (InvocationContext context) => { ... })\
• Option extraction: \context.ParseResult.GetValueForOption(...)\
• Exit code: \context.ExitCode = 1\ in a \inally\ block for non-normal exits
• Uses \isNormalExit\ flag to distinguish 4 normal exit paths (dry-run, skip-graph, missing-tenantId, success) from ~24 error paths

Why context.ExitCode over Environment.Exit(1)?

	Environment.Exit(1)	context.ExitCode = 1
Terminates process?	Yes, immediately	No - natural exit
Output flushing?	May truncate	Completes fully
Cleanup?	Partial	Full

Validation

Tested with real publish error (HTTP 400 'Must upload a newer version'):

	BEFORE (v1.1.62)	AFTER (patched)
Exit code	0 (bug)	1 (fixed)
Output	Complete	Complete
Truncation	None	None

• Full solution build: 0 errors, 0 warnings
• Full test suite: 900 passed, 17 skipped, 0 failed

Related

• See also Publish command: GraphApiService acquires a new token for every Graph API call (no caching in Azure CLI path) #265 (token caching optimization)

[Copilot]

Pull request overview

This PR fixes a critical bug where the publish command always returned exit code 0, even when errors occurred. The root cause was that the SetHandler used a typed-parameter signature returning Task instead of Task<int>, which System.CommandLine interprets as always successful. This prevented calling scripts and CI/CD pipelines from detecting publish failures.

Changes:

• Refactored SetHandler to use InvocationContext pattern for exit code control
• Added isNormalExit flag to track successful completion paths
• Implemented finally block to set context.ExitCode = 1 for all error paths