ci: add a PR gate that actually checks the generated code

[Episkey-G]

Why

This repo has had no GitHub Actions at all — only a .travis.yml, and Travis stopped serving open-source repos long ago. So PRs here currently run zero build and zero tests.

That matters for the codegen PRs specifically: mergeable_state: clean on them right now means "nobody is checking", not "it passed".

What this adds

.github/workflows/ci.yml — three checks plus a single ci-gate aggregator, so branch protection only ever needs one required check name no matter how the jobs are rearranged later.

The gate keeps only what decides whether the generated SDK is actually usable:

job	what it runs	why it's in the gate
ci-syntax	go build ./... + gofmtcheck	covers services/ (the generated packages). Also catches duplicate imports and duplicate declarations — Go treats both as compile errors
lint	go vet ./...	real bug patterns (printf arg mismatch, lock copying, unused assignments), not style
test	make test-cov

Coverage upload is a continue-on-error step inside test and is deliberately not in ci-gate's needs — an upload credential problem must never turn a PR red.

Also: a test that could not pass reliably

TestClientTimeout pointed the client at https://httpbin.org/delay/2, a third-party public service. When that service is unavailable the assertions fail — measured: it returned 503 and the test failed. There is no testing.Short() guard either, so -short cannot skip it. Test_errorHandler had a second reference to the same host.

Both now use a local httptest server. The handler also selects on r.Context().Done(), so it returns as soon as the client times out and srv.Close() does not block.

.travis.yml is removed — it describes a CI that has not run in years, and leaving it implies coverage that does not exist.

Verified locally

make ci-syntax   exit 0
                 exit 2 on an injected syntax error
                 exit 2 on injected gofmt drift
make lint        exit 0
make test-cov    exit 0   (was failing on TestClientTimeout before this)

Not included

A scheduled compatibility matrix. The declared floor in go.mod is go 1.13 and I have not verified the current tree builds on it — shipping that matrix now would just produce a red nightly. Worth doing as a follow-up, together with deciding whether go 1.13 is still the floor we want to claim.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Security Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE