ci: add e2e test to on-pr workflow

[ctran88]

What's New?

• similar to ci: add e2e test to on-pr workflow passage-node#222
• except it also has
  • additional steps to resolve the version based on the release please manifest and go.mod files
  • an additional field in the client payload to set the version

runs

• successful run where version has not changed
• successful run where go.mod major version was bumped and the version passes through the input correctly

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]

this will be an empty string '' if version is not set (no change), which will translate to an empty input for the upstream workflow so that it will grab the version from the release please branch manifest instead