CI: Fall back to main for examples and pass the resource key to pull request tests

[YaroslavVlasenko]

Why:

• https://github.com/51Degrees/ip-intelligence-java/actions/runs/35192147021
• https://github.com/51Degrees/ip-intelligence-java/actions/runs/35191695898
• https://github.com/51Degrees/ip-intelligence-java/actions/runs/35164943716

The Pull Requests workflow fails on any branch that is not main. The three runs above show two separate causes, both in the CI setup.

1. Examples are cloned by the name of the branch under test

ci/run-integration-tests.ps1 and ci/run-performance-tests.ps1 clone ip-intelligence-java-examples with -Branch $Branch, and common-ci fills $Branch with the branch being tested. When the examples repo has no branch with that name the clone stops with:

fatal: Remote branch ci/dispatch-as-dry-run not found in upstream origin

Pairing branches by name was added on purpose in #67 and is kept. The scripts now ask the examples repo whether the branch exists and use main when it does not.

2. The pull request workflows do not pass TestResourceKey

publish.yml and the Publish job of nightly-pipeline.yml pass TestResourceKey, the pull request ones did not. Nobody noticed while the cloud tests were ignored. #178 turns them back on and they fail in setup with "A resource key is required to access the cloud server". The same secret is now passed in pull-requests.yml and in the PullRequests job of nightly-pipeline.yml.

ci/README.md says which examples branch is used.

Notes

• CI takes the scripts and the workflow file from the branch under test, so CI: Let the pull request workflow be dispatched as a dry run #177 and TEST: Run the cloud tests again, and let a property have no value #178 need main merged in after this lands, then a new run. Re-running the old runs builds the old commit.
• Only Ubuntu_ARM_Java_17 is red in those runs because it finishes first and the rest of the matrix is cancelled. It is not ARM specific.
• None of the three runs got as far as the integration or cloud tests, so this change lets them run but does not show that they pass. Cloud web example fails (503) - TestResourceKey not provisioned for IPI cloud #154 reports that the key used by this repo may not be entitled to IP Intelligence cloud. If so, the cloud tests in TEST: Run the cloud tests again, and let a property have no value #178 will still fail, this time with a cloud error.

Tested

The branch check was run in PowerShell against the real examples repo: an existing branch, an existing branch with a slash in its name, two missing branches and a partial name. Both scripts parse and both workflow files are valid YAML. A full run needs CI.