Add CI pipeline using test-framework-template

[dogkeeper886]

Summary

• Install test-framework-template as cicd/ with 7 YAML-driven test cases across 3 suites (build, integration, e2e)
• Add GitHub Actions workflows (test-pipeline.yml, test-suite.yml) triggered on PRs and pushes
• Add CI Docker Compose with PostgreSQL, DB init script, and helper scripts (ci-up.sh, ci-down.sh)

Test Cases

Suite	ID	Name
build	TC-BUILD-001	PHP Syntax Check (via Docker)
build	TC-BUILD-002	Docker Image Build
build	TC-BUILD-003	Composer Dependencies
integration	TC-INTEGRATION-001	TestLink Container Startup
integration	TC-INTEGRATION-002	XML-RPC API Ping
integration	TC-INTEGRATION-003	XML-RPC API Authentication
e2e	TC-E2E-001	Full CRUD Workflow via XML-RPC

Test plan

• All 7 tests pass locally with --no-llm (simple judge)
• GitHub Actions pipeline runs successfully on this PR
• Build suite validates PHP syntax and Docker build
• Integration suite verifies API responds correctly
• E2E suite completes full create/verify/teardown cycle

Closes #2

🤖 Generated with Claude Code

[dogkeeper886]

Self-review: Changes requested

Checklist

Category	Status	Notes
Issue linkage	✅	Closes #2
Title	✅	47 chars, clear
Code quality	✅	No secrets, no debug code
Tests pass locally	✅	7/7 pass
CI passes	❌	Integration tests fail on GitHub Actions

Issues

1. Double environment startup: test-suite.yml has a "Start CI environment" step for integration/e2e suites, but TC-INTEGRATION-001 also calls ci-up.sh. Pick one — either the workflow manages the environment or the test cases do.

2. Integration tests fail in CI: The runner builds and starts Docker containers, but the "Check test results" step fails. Need to investigate the runner logs to determine root cause (likely context path or timing issue).

Recommendation

Fix the double-startup issue, then re-push and check CI. If the CI runner environment is fundamentally different (e.g. Docker Compose build context), may need to adjust ci-up.sh or the workflow to handle it.