[CI] Add upload pr_number artifacts action to ci-e2e-all.yml

[pipiland2612]

Which problem is this PR solving?

• Resolves part of Implement framework to validate backwards compatibility of metrics #6278
• Supports [CI] Add new post comment workflow #7414

Description of the changes

• Add upload pr_number artifacts action
• The ci-comment.yml workflow can now detect pr number by downloading the artifact

How was this change tested?

• from my repostory pull request: error pipiland2612/jaeger#2
• log from the action https://github.com/pipiland2612/jaeger/actions/runs/16997159461/job/48190513998:

Successfully extracted metrics_snapshot_elasticsearch_8.x_v2
Processing artifact: diff_metrics_snapshot_elasticsearch_8.x_v2 (ID: 3776313824)
Extracting to /home/runner/work/jaeger/jaeger/.metrics/diff_metrics_snapshot_elasticsearch_8.x_v2
Successfully extracted diff_metrics_snapshot_elasticsearch_8.x_v2

Starting PR number detection...
Workflow run details:
- Head branch: error_branch
- Head repository: pipiland2612/jaeger
- Commit SHA: 49af2ee184cc536901005ca2af043cb32ad1e493

Attempt 1: Searching PRs for branch pipiland2612/jaeger:error_branch
Found PR Number from artifact: 2

Final PR Number: 2

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[pipiland2612]

Hi @yurishkuro, I think this could solve our CI error: Could not determine PR number for commenting. I have tested in my own forked and it's good. Hope we can finish this soon!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.63%. Comparing base (97f40a9) to head (95d0b38).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7448   +/-   ##
=======================================
  Coverage   96.63%   96.63%           
=======================================
  Files         377      377           
  Lines       23089    23089           
=======================================
  Hits        22312    22312           
  Misses        592      592           
  Partials      185      185           

Flag	Coverage Δ
badger_v1	9.02% <ø> (ø)
badger_v2	1.70% <ø> (ø)
cassandra-4.x-v1-manual	11.68% <ø> (ø)
cassandra-4.x-v2-auto	1.69% <ø> (ø)
cassandra-4.x-v2-manual	1.69% <ø> (ø)
cassandra-5.x-v1-manual	11.68% <ø> (ø)
cassandra-5.x-v2-auto	1.69% <ø> (ø)
cassandra-5.x-v2-manual	1.69% <ø> (ø)
elasticsearch-6.x-v1	16.58% <ø> (ø)
elasticsearch-7.x-v1	16.62% <ø> (ø)
elasticsearch-8.x-v1	16.77% <ø> (ø)
elasticsearch-8.x-v2	1.70% <ø> (ø)
elasticsearch-9.x-v2	1.70% <ø> (ø)
grpc_v1	10.22% <ø> (ø)
grpc_v2	1.70% <ø> (ø)
kafka-3.x-v1	9.67% <ø> (ø)
kafka-3.x-v2	1.70% <ø> (ø)
memory_v2	1.70% <ø> (ø)
opensearch-1.x-v1	16.67% <ø> (ø)
opensearch-2.x-v1	16.67% <ø> (ø)
opensearch-2.x-v2	1.70% <ø> (ø)
opensearch-3.x-v2	1.70% <ø> (ø)
query	1.70% <ø> (ø)
tailsampling-processor	0.47% <ø> (ø)
unittests	95.62% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 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.

[pipiland2612]

When this is merged, I think we can rerun the CI in the testing pr