ci: Add target release version labels to merged PRs

[nuno-faria]

Which issue does this PR close?

• Closes Track PR release version with labels/milestones #25280.

Rationale for this change

Adds a release version label to merged PRs so it's easy to determine which version a PR will land/has landed.

What changes are included in this PR?

• New workflow.
• Updated the dev/update_datafusion_versions.py script to automatically update the version in the workflow.

What is the testing strategy for this PR?

This PR.

Are there any user-facing changes?

No.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.51%. Comparing base (6a792c6) to head (2f2359d).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #25776      +/-   ##
==========================================
+ Coverage   82.49%   82.51%   +0.01%     
==========================================
  Files        1140     1141       +1     
  Lines      438555   439780    +1225     
  Branches   438555   439780    +1225     
==========================================
+ Hits       361803   362884    +1081     
- Misses      54880    54953      +73     
- Partials    21872    21943      +71     

☔ View full report in Codecov by Harness.
📢 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.

[nuno-faria]

I'm not sure if its possible to test this without merging to main, as it requires additional permissions to create the label:

https://github.com/apache/datafusion/actions/runs/36247423656/job/108419093281

POST /repos/apache/datafusion/labels - 403 with id 2040:283A1E:2A73CD0:8D1DC93:6AB7D19E in 127ms
RequestError [HttpError]: Resource not accessible by integration - https://docs.github.com/rest/issues/labels#create-a-label
    at fetchWrapper (/home/runner/work/_actions/actions/github-script/v9.0.0/dist/index.js:61509:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async eval (eval at callAsyncFunction (/home/runner/work/_actions/actions/github-script/v9.0.0/dist/index.js:64949:16), <anonymous>:14:5)
    at async main (/home/runner/work/_actions/actions/github-script/v9.0.0/dist/index.js:65100:20) {

[alamb]

Let's give it a try -- thanks @nuno-faria

[alamb]

maybe we could drive this from a data file rather than an inline script (maybe we could even start updating the version on main before we cut a new release 🤔 )

[nuno-faria]

Thanks @alamb, I moved the script to a file.
This is already intended to start now, target_version is set to 56 since new PRs will target the next version, so they get the label "v56" (sorry if I misunderstood your question).

[alamb]

Sounds great -- thank you -- let's try it

[alamb]

Thanks @nuno-faria -- I'll merge this in and we can give it a try.

If people find it useful, we can always send an agent / script to update existing PRs with backdated release information

[nuno-faria]

When moving the script to a dedicated file I forgot to checkout the code, so it is currently failing: https://github.com/apache/datafusion/actions/runs/36464821849. I'll try to fix it.

[nuno-faria]

Hopefully fixed by #25845.