ci: add allow_failure to all manual jobs to prevent pipeline hanging

[Leiyks]

Description

Manual jobs without allow_failure block pipeline completion by default. This causes pipelines to stay in "running" state indefinitely even when all actual jobs have completed, because GitLab waits for manual jobs to be triggered.

Added |allow_failure: true to all manual jobs:

• CI image builds (CentOS, Alpine, Bookworm, Buster)
• Benchmarks (tracer, profiling, appsec)
• Macrobenchmarks
• Package deployment jobs
• AppSec docker image pushes
• Tested versions collection

Also added allow_failure to the deploy_to_reliability_env trigger job to prevent hanging when downstream pipelines don't complete.

This allows pipelines to complete successfully while keeping manual jobs available for optional execution.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 62.12%. Comparing base (ee75439) to head (072a995).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3649      +/-   ##
==========================================
+ Coverage   62.11%   62.12%   +0.01%     
==========================================
  Files         141      141              
  Lines       13387    13387              
  Branches     1753     1753              
==========================================
+ Hits         8315     8317       +2     
+ Misses       4273     4270       -3     
- Partials      799      800       +1     

see 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ee75439...072a995. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[datadog-datadog-prod-us1]

⚠️ Tests

✨ Fix all issues with Cursor

⚠️ Warnings

🧪 1026 Tests failed

    testSearchPhpBinaries from integration.DDTrace\Tests\Integration\PHPInstallerTest (Fix with Cursor)

testSimplePushAndProcess from laravel-58-test.DDTrace\Tests\Integrations\Laravel\V5_8\QueueTest (Datadog) (Fix with Cursor)

DDTrace\Tests\Integrations\Laravel\V5_8\QueueTest::testSimplePushAndProcess
Test code or tested code printed unexpected output: spanLinksTraceId: 698f490300000000075398ea6a415999
tid: 698f490300000000
hexProcessTraceId: 075398ea6a415999
hexProcessSpanId: 57b189696e52571b
processTraceId: 527933713904916889
processSpanId: 6318982838092977947

phpvfscomposer://tests/vendor/phpunit/phpunit/phpunit:106

testSimplePushAndProcess from laravel-8x-test.DDTrace\Tests\Integrations\Laravel\V8_x\QueueTest (Datadog) (Fix with Cursor)

DDTrace\Tests\Integrations\Laravel\V8_x\QueueTest::testSimplePushAndProcess
Test code or tested code printed unexpected output: spanLinksTraceId: 698f48f900000000b4d90c199017cbee
tid: 698f48f900000000
hexProcessTraceId: b4d90c199017cbee
hexProcessSpanId: dc10d6ee8f00bc70
processTraceId: 13031460300704435182
processSpanId: 15857410608061267056

phpvfscomposer://tests/vendor/phpunit/phpunit/phpunit:106

View all

ℹ️ Info

❄️ No new flaky tests detected

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 072a995 | Docs | Datadog PR Page | Was this helpful? Give us feedback!}