Cancel integrations early when platform provisioning fails; improve the provisioning process

Immediate Issue

• Current behavior: Integrations continue running even when a platform enters an error state during provisioning. This wastes CI resources and time.
• Expected behavior: Cancel integrations as soon as any platform enters an error state during provisioning."

Long-Term Goals

• Make the provisioning process more reliable across all platforms.
• Investigate potential logging and reporting improvements to help diagnose and track provisioning failures.
• Recommend hiring or outsourcing a network specialist to address known intermittent connectivity issues in the CI system.

Steps to Reproduce:

1. Start an integration.
2. Example integration: http://coin/coin/integration/qt/qt5/tasks/1741242028 (corporate internal link).
   • The integration started at 5:00 PM.
   • The macOS 14 platform failed provisioning at 5:42 PM and entered an error state.
   • The integration continued running on other platforms until 5:53 AM, citing the first failed platform as the reason for cancellation.

Acceptance Criteria:

1. Immediate Fix
   • Cancel integrations as soon as any platform enters an error state during provisioning."
2. Long-Term Improvements
   • Make the provisioning process more robust across all platforms.
   • Implement logging and reporting improvements to help diagnose failures.
   • Document the recommendation to hire or outsource a network specialist.