Resolve target definition variables during p2 repository assembly

[kysmith-csg]

Recreation of #3042 to account for new base branch (master vs v4.0.x).

[github-actions]

Test Results

   570 files  ±0     570 suites  ±0   3h 48m 55s ⏱️ + 30m 7s
   374 tests ±0     368 ✔️ ±0    6 💤 ±0  0 ❌ ±0 
1 122 runs  ±0  1 103 ✔️ ±0  19 💤 ±0  0 ❌ ±0 

Results for commit 555fc3c. ± Comparison against base commit 73fb931.

[HannesWell]

Perfect.
Thank you.

[github-actions]

💔 All backports failed

Status	Branch	Result
❌	tycho-4.0.x	Backport failed because of merge conflicts

Manual backport

To create the backport manually run:

backport --pr 3049

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

[HannesWell]

💔 All backports failed

Status Branch Result
❌ tycho-4.0.x Backport failed because of merge conflicts

OK, looks like this was a bad example to demonstrate the automated back-port feature. :/

Can you just re-open #3042 to handle the 'back-porting'?

[kysmith-csg]

@HannesWell I am not able to reopen pull requests so I've opened #3051.

[HannesWell]

@HannesWell I am not able to reopen pull requests so I've opened #3051.

Thanks.
From my experience one can only reopen a closed PR if the branch still exists and points to the exact commit it pointed last when the PR was closed. But additionally this might also require commiter rights (I'm not sure about that).