Add GitHub Actions workflow for PR integration tests against UAA

[duanemay]

Summary

Ports the Concourse uaa-singular-tests job (concourse/pull-requests/pipeline.yml in uaa-ci) to a self-contained GitHub Actions workflow (.github/workflows/pull-request-integration.yml) that runs on every pull request:

1. Checks out this PR and cloudfoundry/uaa (develop, public repo — no deploy key needed)
2. Builds UAA's bootWar and boots it, polling /uaa for readiness
3. Creates the singular-test-client OAuth client via the admin API (same payload the Concourse task and local test/startUAA.sh use)
4. Installs deps, then installs a chromedriver version matching the runner's Chrome major version at runtime (same pattern the existing Concourse task already uses — never commit a pinned/downgraded version)
5. Starts the static app server and runs npm test (build + unit + Nightwatch integration)

Differences from the Concourse version, and why:

• No dependency on the private uaa-ci repo for the shared task script — the logic is inlined directly, since a public-repo pull_request workflow (including fork PRs) shouldn't depend on a private repo.
• No explicit PR status put steps — GitHub Actions reports the job's pass/fail as the PR check natively.
• No privileged: true container — nightwatch.json already runs Chrome with --no-sandbox, and GitHub's ubuntu-latest runners ship Chrome preinstalled.
• Uses pull_request (not pull_request_target): runs with the fork's code and no repo secrets, since none are needed for this job.

Also adds pull_request to unit-test.yml's trigger (alongside the existing push). push-triggered workflows only run in a fork's own Actions context, not upstream, so external contributors' PRs currently get no build/unit-test check at all. Same-repo branches will now run that job twice per commit once a PR is open (push + pull_request) — an accepted, minor cost for a job this cheap.

Test plan

• Confirm both workflows run successfully on this PR (validates the full UAA build/boot/test flow works in GitHub Actions, and that unit-test now triggers on pull_request)
• Manually verified the equivalent local flow (build UAA, boot via gradlew, create test client, npm test) succeeds end-to-end

🤖 Generated with Claude Code

[Copilot]

Pull request overview

Adds a self-contained GitHub Actions workflow to run the existing UAA + Singular end-to-end integration flow on every PR, replacing the need for the Concourse uaa-singular-tests job for PR validation.

Changes:

• Introduces a pull_request workflow that checks out this repo and cloudfoundry/uaa (develop), builds UAA, boots it, and waits for readiness.
• Creates the singular-test-client via UAA’s admin API, then installs Node deps + a Chrome-major-matched chromedriver.
• Starts the local static server and runs npm test (build + unit + Nightwatch integration).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.