taxonomy: add GitLab CI slug

[SulimanAbdulrazzaq]

What does this PR do, and why does it fit the north star?

Adds infra/gitlab-ci to the closed skill taxonomy and advances its version from 1.14.0 to 1.15.0.

GitLab CI is a distinct, widely used CI platform whose .gitlab-ci.yml and .gitlab/ci/*.yml paths can provide deterministic local evidence. Adding the slug first keeps vocabulary review separate from the dependent signature work required by #24.

Checklist

• Tests pass locally (npm test) — the default 5-second Windows fixture timeout is reproducibly too short on this machine; the exact failed test passes with a 30-second timeout
• npm run typecheck passes

If this adds or changes a detection signature

• Includes positive and negative fixtures — not applicable to this taxonomy-only prerequisite
• The slug already exists — not applicable; this PR adds the prerequisite vocabulary entry

If this touches WHAT data leaves the machine, or WHERE it's sent

• Links the prior discussion issue: CI-platform signatures: GitLab CI, CircleCI, Jenkins (pick one) #24
• Schema version and docs/schema.md updated — not applicable; the bundle schema is unchanged
• Relevant privacy/taxonomy contract tests run

If this adds a new runtime dependency

• Written justification included — not applicable; no dependency changes

Docs and changelog

• CHANGELOG.md entry added under [Unreleased]
• Relevant doc updated — not applicable to the vocabulary-only prerequisite

Additional context

The branch is updated with current upstream main, including the Razorpay and Okta taxonomy entries at version 1.14.0.

Validation:

• npm run typecheck: passed
• npm run build: passed
• package-map, skill-detect, and taxonomy contract tests: 133 passed
• test/privacy/submit-guardrail.test.ts --testTimeout=30000 --hookTimeout=30000: 4 passed
• git diff --check: passed

The Windows Node 20 CI failure is a single 5-second timeout in submit-guardrail.test.ts; 862/863 tests passed. The same upstream SHA passes Windows Node 20, all other matrix jobs pass, and the taxonomy-only diff does not touch that test or runtime path.

This PR intentionally references rather than closes #24. The GitLab CI signature, positive and near-miss fixtures, and changelog entry remain a separate follow-up after this slug is merged.

[SulimanAbdulrazzaq]

The Windows Node 20 failure appears timing-related rather than caused by this taxonomy-only diff: CI passed 862/863 tests and timed out only in submit-guardrail at the 5-second limit, while the same current upstream SHA passes that job. Locally, the exact test passes 4/4 with a 30-second timeout; typecheck, build, and the 133 taxonomy-related tests also pass. I cannot rerun repository Actions from the fork, so a maintainer rerun of the failed job would be appreciated.

[jpbelmo]

Your diagnosis is exactly right, and it's our flake, not your diff: third file with the same Windows 5s-timeout pattern this week. Rerun was already launched when your comment landed; it's running now. A repo-side fix raising those fixture-test timeouts is queued. Thanks for the textbook triage, local repro included.

[SulimanAbdulrazzaq]

Thanks for confirming the diagnosis and rerunning the job. I’ll keep the GitLab CI detection work as the separate follow-up required by #24.