SWA functional tests failed repeatedly in Linux and Windows

[Alirexaa]

Linux build: https://github.com/CommunityToolkit/Aspire/actions/runs/14876614569/job/41775040787?pr=676
Windows build: https://github.com/CommunityToolkit/Aspire/actions/runs/14876614569/job/41775057456?pr=676

🔴 CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests (.NETCoreApp,Version=v8.0)

✓  Passed	✘  Failed	↷  Skipped	∑  Total	⧗  Elapsed
9	2	—	11	24s

• SwaHostingComponentTests (2 failed)
  • 🟥 CanAccessApiSuccessfully

    Aspire.Hosting.DistributedApplicationException : Stopped waiting for resource 'swa' to become healthy because it failed to start.
       at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitForResourceHealthyAsync(String resourceName, WaitBehavior waitBehavior, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 282
       at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitForResourceHealthyAsync(String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 243
       at CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessApiSuccessfully() in D:\a\Aspire\Aspire\tests\CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests\SwaHostingComponentTests.cs:line 25
    --- End of stack trace from previous location ---

  • 🟥 CanAccessFrontendSuccessfully

    Aspire.Hosting.DistributedApplicationException : Stopped waiting for resource 'swa' to become healthy because it failed to start.
       at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitForResourceHealthyAsync(String resourceName, WaitBehavior waitBehavior, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 282
       at Aspire.Hosting.ApplicationModel.ResourceNotificationService.WaitForResourceHealthyAsync(String resourceName, CancellationToken cancellationToken) in /_/src/Aspire.Hosting/ApplicationModel/ResourceNotificationService.cs:line 243
       at CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests.SwaHostingComponentTests.CanAccessFrontendSuccessfully() in D:\a\Aspire\Aspire\tests\CommunityToolkit.Aspire.Hosting.Azure.StaticWebApps.Tests\SwaHostingComponentTests.cs:line 13
    --- End of stack trace from previous location ---

[Alirexaa]

/cc @aaronpowell

[aaronpowell]

I need to find time to revisit this integration, as it's one of the first I ever built so I don't think I did it with the level of resilience that I would use today, and that could be contributing to the failures.

[aaronpowell]

Looks like this is blocking the release to support 9.3, I'll try and get that fixed in between Build stuff