Re-enable E2E testing for the 5.8 branch

[desrosj]

[52449] adjusted the workflow for testing old branches after creating the 5.9 branch.

For E2E tests, only the most recent supported branch is tested regularly. But as of 5.8, there are more tests than just “Hello World” ones (see #52905), so the same pattern as PHP Compatibility testing should be used for E2E tests going forward.

[hellofromTonya]

There are a total of 3 e2e tests on the 5.8 branch:

• 2 for Quick Draft
• 1 for "Hello World"

Though the coverage is tiny, if a regression does happen in those coverage areas, then there's an advantage for running them as they might reveal it. Performance-wise, running these 3 tests should be quick.

Overall, I think it is worth wiring up these tests to run. Thumbs up from me!

[davidbaumwald]

In 52546:

Build/Test Tools: Re-enable E2E tests for the 5.8 branch.

After the 5.9 branch was created, [52449] updated the workflow for testing old branches to include 5.9. However, the E2E tests -branch condition was updated to 5.9 instead of adding an additional branch condition for 5.9. This commit re-enables the E2E tests for 5.8.

Props desrosj, hellofromTonya.
Fixes #54749.

[davidbaumwald]

Reopening for backport to the 5.9 branch.

[hellofromTonya]

👍 for backport

[hellofromTonya]

@davidbaumwald @desrosj is this on your radar for backport to 5.9?

[desrosj]

In GitHub Actions, scheduled events only run in the repositories primary branch. Since this change was made in trunk already, we can just close this out as fixed and leave as 5.9 to reflect when the change was made.

I go back and forth for when to include changes to these files in backports (keeping the files up to date is easier when backporting other changes), but I think it makes more sense to leave these files as they are when branching occurs, or to remove them entirely.

We can close this one out, and when the next round of GHA related backports occurs, I can make a final decision here.