Custom Transport Configuration support

[dlabey]

• Adds the concept of TransportConfiguration for
• Adds support for setting a custom HTTP status code in the performCall method or use the same default bad request

Fixes #372

[armando-rodriguez-cko]

Please @dlabey review all the tests, some test are failing

[dlabey]

@armando-rodriguez-cko because I am on a fork I am not inheriting the IT secrets from the GitHub environment, and the tests have hardcoded processing channels... how do you advise I proceed?

[dlabey]

@armando-rodriguez-cko I changed the build-pull-request file to use pull_request_target so it inherits the context of the source repo. According to https://blog.gitguardian.com/github-actions-security-cheat-sheet/, this can be insecure unless you manually approve the execution of workflows, which you are doing, so maybe this will help.

[armando-rodriguez-cko]

Hi @dlabey, thank you for the changes but we can't admit the last commit, as you say this change is insecure. We will pass the tests with your previous changes and tell you how to proceed. Thank you.

[dlabey]

@armando-rodriguez-cko I have merged it back, could you checkout this branch and run it with the secrets locally? Or could you take this branch and put it into the checkout owned repo for a PR to inherit the secrets?

[dlabey]

@armando-rodriguez-cko any update? I cannot run the IT properly because my fork does not inherit the IT Checkout API keys which are coupled to the processing channels used in the IT tests...

[armando-rodriguez-cko]

Hi @dlabey, we are working on it, sorry by the delay, we will try to finish it today.