Fix GitLab webhook response status code

[vigo]

Summary

• Change GitLab webhook response from 202 Accepted to 200 OK
• Per GitLab's documentation: "Respond quickly with a 200 or 201 status"

Reference

https://docs.gitlab.com/ee/user/project/integrations/webhooks.html

🤖 Generated with Claude Code

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
.../http/gitlabwebhookhandler/gitlabwebhookhandler.go	98.63% <100.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[Copilot]

Pull request overview

This PR updates the GitLab webhook handler to comply with GitLab's webhook documentation by changing the HTTP response status code from 202 Accepted to 200 OK. The change aligns with GitLab's requirement to "Respond quickly with a 200 or 201 status."

• Changed webhook success response from HTTP 202 to HTTP 200
• Updated all corresponding test assertions to match the new status code

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
internal/transport/http/gitlabwebhookhandler/gitlabwebhookhandler.go	Updated the success response status code from 202 Accepted to 200 OK
internal/transport/http/gitlabwebhookhandler/gitlabwebhookhandler_test.go	Updated all 6 test cases to assert the new 200 OK status code instead of 202 Accepted

---

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