feat: Add v1.2.2 schema with conda package manager support

[LittleCoinCoin]

Summary

Implements v1.2.2 package schema with support for conda package manager and channel specification, enabling packages to specify conda as an alternative to pip for Python dependencies.

Changes

Core Infrastructure

• feat(core): Add get_python_dependency_channel() method to PackageAccessorBase
  • Provides foundation for conda channel support
  • Returns None by default for backward compatibility

Feature Implementation

• feat(schema): Complete v1.2.2 package schema implementation
  • PackageAccessorV1_2_2: Metadata accessor with conda channel support
  • PackageValidatorV1_2_2: Validator chain with delegation to v1.2.1
  • SchemaValidationStrategyV1_2_2: Schema validation for v1.2.2 format
  • DependencyValidationStrategyV1_2_2: Enhanced dependency validation

Integration

• feat(factory): Register v1.2.2 components in factory classes

  • PackageAccessorFactory: Register PackageAccessorV1_2_2
  • ValidatorFactory: Register PackageValidatorV1_2_2

• feat(service): Add conda channel retrieval to PackageService

  • Expose get_python_dependency_channel() through service layer
  • Maintains backward compatibility with earlier versions

Bug Fixes

• fix(accessor): Correct v1.2.1 entry point return type
  • Fixed get_entry_point() to return full dict instead of string
  • Resolves test failures in test_package_service.py

Testing

• test(v1.2.2): Comprehensive test coverage (15 tests, all passing)
  • 13 unit tests covering all validation scenarios
  • 2 integration tests for end-to-end workflows
  • Tests for conda packages, pip packages, and mixed dependencies
  • Channel validation and format testing

Features

Conda Package Manager Support

• Python dependencies can specify package_manager: "conda" or package_manager: "pip"
• Defaults to pip when package_manager is not specified
• Conda packages support optional channel field (e.g., "conda-forge", "bioconda")

Validation Rules

• ✅ Conda packages can have optional channel
• ✅ Pip packages cannot have channel (validation error if present)
• ✅ Invalid package managers are rejected
• ✅ Channel format is validated (alphanumeric, hyphens, underscores)
• ✅ Mixed pip and conda dependencies are supported

Backward Compatibility

• Full delegation to v1.2.1 for unchanged operations
• Proper chain of responsibility pattern maintained
• All existing tests continue to pass

Example Usage

schema_version: "1.2.2"
python_dependencies:
  - name: numpy
    version: ">=1.20.0"
    package_manager: conda
    channel: conda-forge
  - name: pandas
    version: ">=1.3.0"
    package_manager: pip

Test Results

✅ V1.2.2 tests: 15/15 passing
✅ Package service tests: 4/4 passing
✅ Schema validators: 13/13 passing
✅ Registry service: 16/16 passing
✅ Dependency graph: 22/22 passing
✅ Total: 70+ tests passing

Commit Structure

Follows organization's conventional commit format:

1. feat(core): Base accessor infrastructure
2. feat(schema): v1.2.2 implementation
3. feat(factory): Factory registration
4. feat(service): Service layer enhancement
5. fix(accessor): v1.2.1 bug fix
6. test(v1.2.2): Comprehensive test coverage

Checklist

• All tests pass
• Conventional commit format followed
• Backward compatibility maintained
• Comprehensive test coverage added
• Code follows chain of responsibility pattern
• Documentation in code is clear and complete

Related Issues

Implements support for conda package manager as requested for enhanced package management flexibility.

---

Pull Request opened by Augment Code with guidance from the PR author