feat: Add GitHub Releases API support

[ralflang]

Summary

Add comprehensive support for the GitHub Releases API, enabling creation, retrieval, updates, and asset uploads for releases.

Features

API Methods (4 new)

• createRelease() - Create a new release for an existing tag
• getReleaseByTag() - Retrieve a release by tag name
• updateRelease() - Update release metadata (name, body, draft/prerelease status)
• uploadReleaseAsset() - Upload binary assets (zips, tarballs, executables, etc.) to releases

Value Objects

• GithubRelease - Represents a release with 12 properties including assets array
• GithubReleaseAsset - Represents uploaded assets with 10 properties (id, name, size, download count, etc.)

DTOs

• CreateReleaseParams
  • Required: tagName
  • Optional: name, body, draft, prerelease, targetCommitish
• UpdateReleaseParams
  • All fields optional: tagName, name, body, draft, prerelease
  • Includes isEmpty() helper method

Request Factories

• CreateReleaseRequestFactory - POST /repos/{owner}/{repo}/releases
• GetReleaseByTagRequestFactory - GET /repos/{owner}/{repo}/releases/tags/{tag}
• UpdateReleaseRequestFactory - PATCH /repos/{owner}/{repo}/releases/{id}
• UploadReleaseAssetRequestFactory - POST to upload_url (handles template URL format)

Implementation Details

• Follows existing codebase patterns:
  • Request Factory pattern for API endpoints
  • Value Objects with fromApiResponse() static factories
  • DTOs with toArray() for request payloads
• StreamFactory requirement for write operations (create, update, upload)
• Proper URL encoding for tag names
• Handles GitHub's template URLs for asset uploads

Dependencies Added

• psr/http-client ^1.0 (PSR-18)
• psr/http-factory ^1.0 (PSR-17)
• psr/http-message ^2.0 (PSR-7)

Testing

Test Coverage

• 58 new unit tests covering all release functionality
• Total: 143 tests, 478 assertions, all passing ✅

Test Categories

• DTOs: construction, toArray(), validation
• Value Objects: fromApiResponse() with complete/minimal/edge case data
• GithubApiClient methods: success cases, error cases (404, 422, 401, 403)
• StreamFactory requirement validation
• Multiple assets handling
• Different content types and states

Example Usage

use Horde\GithubApiClient\GithubApiClient;
use Horde\GithubApiClient\GithubRepository;
use Horde\GithubApiClient\CreateReleaseParams;

// Create a release
$repo = GithubRepository::fromFullName('horde/GithubApiClient');
$params = new CreateReleaseParams(
    tagName: 'v1.0.0',
    name: 'Version 1.0.0',
    body: 'First stable release',
    draft: false,
    prerelease: false
);
$release = $client->createRelease($repo, $params);

// Upload an asset
$asset = $client->uploadReleaseAsset(
    uploadUrl: $release->uploadUrl,
    filename: 'release.zip',
    fileContent: file_get_contents('release.zip'),
    contentType: 'application/zip'
);

// Update release
$updateParams = new UpdateReleaseParams(
    body: 'Updated release notes'
);
$updated = $client->updateRelease($repo, $release->id, $updateParams);

// Get release by tag
$release = $client->getReleaseByTag($repo, 'v1.0.0');

Checklist

• Implementation follows existing patterns
• All methods have proper type hints
• Comprehensive unit tests (100% coverage for new code)
• All tests passing
• PSR standards followed (PSR-7, PSR-17, PSR-18)
• Conventional Commit message format
• Documentation in code (PHPDoc)