Make Azure DevOps pipeline conditions cancellable

[Copilot]

Azure DevOps conditions without explicit status checks may continue running after cancellation. This change adds cancellation-aware guards to executable condition: blocks across the repository.

Changes

• Added succeeded() to conditions that should run only after successful predecessors.
• Replaced always() with succeededOrFailed() for cleanup, diagnostics, and artifact publishing.
• Preserved caller-supplied failure behavior while preventing execution after cancellation.
• Left non-executable condition parameter defaults unchanged.

condition: and(succeeded(), ne(variables['Skip.Test'], 'true'))

condition: and(succeededOrFailed(), failed())

[azure-pipelines]

Azure Pipelines:
Successfully started running 5 pipeline(s).
31 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Mike Harder (mikeharder)]

Copilot: revert any lines where the "before" condition included "always()" or "failed()"

[Mike Harder (mikeharder)]

Copilot: revert any lines where the "before" condition included "always()" or "failed()"