Fix: allow Build/Publish stages to proceed on SucceededWithIssues

The cryptography ceiling check runs with continueOnError: true, which
causes the CI stage to finish as SucceededWithIssues rather than
Succeeded. The strict eq(..., 'Succeeded') conditions on Build,
PublishMSALPython, and PublishPyPI stages caused them to skip.

Change all three conditions to use in(..., 'Succeeded',
'SucceededWithIssues') so warning-only tasks don't block the release.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: RyAuld

.Pipelines/pipeline-publish.yml

@@ -44,7 +44,7 @@ stages:
 - stage: Build
   displayName: 'Build package'
   dependsOn: CI
-  condition: eq(dependencies.CI.result, 'Succeeded')
+  condition: in(dependencies.CI.result, 'Succeeded', 'SucceededWithIssues')
   jobs:
   - job: BuildDist
     displayName: 'Build sdist + wheel (Python 3.12)'
@@ -83,7 +83,7 @@ stages:
   dependsOn: Build
   condition: >
     and(
-      eq(dependencies.Build.result, 'Succeeded'),
+      in(dependencies.Build.result, 'Succeeded', 'SucceededWithIssues'),
       eq('${{ parameters.publishTarget }}', 'test.pypi.org (Preview / RC)')
     )
   jobs:
@@ -140,7 +140,7 @@ stages:
   dependsOn: Build
   condition: >
     and(
-      eq(dependencies.Build.result, 'Succeeded'),
+      in(dependencies.Build.result, 'Succeeded', 'SucceededWithIssues'),
       eq('${{ parameters.publishTarget }}', 'pypi.org (ESRP Production)')
     )
   jobs: