Set up workflow for automated version increments in pull-requests

[HannesWell]

Set up for this repository the workflow for automated version increments in pull-requests added via eclipse-platform/eclipse.platform.releng.aggregator#2352

Before this can work complete, the EF infra team has to add the required PAT of the Platform-bot to this repo as described in the linked PR and requested in

• https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5020#note_2825941

[github-actions]

Test Results

 1 815 files  ±0   1 815 suites  ±0   1h 36m 50s ⏱️ + 1m 13s
 7 699 tests ±0   7 471 ✅ ±0  228 💤 ±0  0 ❌ ±0 
24 258 runs  ±0  23 511 ✅ ±0  747 💤 ±0  0 ❌ ±0 

Results for commit dc31640. ± Comparison against base commit c603575.

[jukzi]

It would be nice if this could be tested with significant PR before rolling it out to every repo.
With significant PR i mean something non trivial like

• needs multiple versions bumps
• not all needed version bumps are reported in the first build
• as a result a feature needs to be updated.

[HannesWell]

eclipse-pde/eclipse.pde#1413

It would be nice if this could be tested with significant PR before rolling it out to every repo.
With significant PR i mean something non trivial like

That has been done extensively and it worked well in:

• [JUST TO TEST] Some first change in a release-cycle eclipse-pde/eclipse.pde#1413
• [JUST TO TEST] Some first change in a release-cycle by non-committer eclipse-pde/eclipse.pde#1414

and before that in my PDE fork:
https://github.com/HannesWell/eclipse.pde/pulls

Of course committers should still check the entire content of a PR as usual.

[HannesWell]

The PAT has been added via eclipse-equinox/.eclipsefdn#1, so this is ready for submission.

For eclipse.platform I have already verified it works.