ci: add e2e test to on-pr workflow

[ctran88]

What's New?

• runs the e2e test suite on pull request
• a team member is expected to at least have write permissions on this repo. successful permissions check and e2e test run here
• an OS contributor is expected to only have read permissions on this repo. successful permissions check here

Screenshots (if appropriate):

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have manually tested my code thoroughly
• I have added/updated inline documentation for public facing interfaces if relevant
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing integration and unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

Additional context

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[ctran88]

i tried using the pull_request. author_association event data as described in https://michaelheap.com/github-actions-check-permission/, but found the results to not be lined up with what was described in the blog.

other people seemed to experience the same behavior (ref, ref)