Remove dagger dependencies and replace with uv scripts

This PR targets the following PR:

• feat: Add JSON schema generation to build process for schemastore.org registration #700

Summary

Completely replaces the dagger-based containerized build system with uv scripts using inline dependencies. This change resolves the /poe build slash command failures in GitHub Actions caused by missing dagger dependencies, while maintaining identical functionality for generating pydantic models and JSON schemas from YAML files.

Key Changes:

• Replaced dagger containerization with uv scripts that declare inline dependencies (datamodel-code-generator==0.26.3, PyYAML>=6.0.1)
• Converted async dagger operations to synchronous subprocess calls using subprocess.run()
• Updated shell script to use uv run instead of pip install dagger-io==0.13.3
• Preserved all datamodel-codegen command line arguments exactly as they were
• Maintained post-processing logic for pydantic v1 imports and deprecated field handling

Review & Testing Checklist for Human

• Verify generated models are identical - Compare airbyte_cdk/sources/declarative/models/declarative_component_schema.py before/after this change to ensure byte-for-byte identical output
• Test CI functionality - Verify that /poe build slash command now works in GitHub Actions without dagger dependency errors
• Test local build process - Run poetry run poe build locally and confirm it completes successfully with same output
• Verify JSON schema generation - Confirm airbyte_cdk/sources/declarative/generated/declarative_component_schema.json is still generated correctly
• Check uv dependency isolation - Ensure datamodel-codegen dependencies don't leak into the main environment

Recommended Test Plan:

1. Take a snapshot of current generated files
2. Run the build process with these changes
3. Compare generated files byte-for-byte
4. Test both local execution and CI execution
5. Verify the original dagger container behavior is fully replicated

Diagram

%%{ init : { "theme" : "default" }}%%
graph TB
    subgraph Legend
        L1[Major Edit]:::major-edit
        L2[Minor Edit]:::minor-edit  
        L3[Context/No Edit]:::context
    end

    YamlSchema["airbyte_cdk/sources/declarative/<br/>declarative_component_schema.yaml"]:::context
    
    BuildScript["bin/generate_component_manifest_files.py"]:::major-edit
    ShellScript["bin/generate-component-manifest-dagger.sh"]:::major-edit
    
    PyprojectToml["pyproject.toml<br/>(poe assemble task)"]:::context
    
    GeneratedModels["airbyte_cdk/sources/declarative/models/<br/>declarative_component_schema.py"]:::context
    GeneratedJson["airbyte_cdk/sources/declarative/generated/<br/>declarative_component_schema.json"]:::context
    
    YamlSchema --> BuildScript
    BuildScript --> GeneratedModels
    BuildScript --> GeneratedJson
    ShellScript --> BuildScript
    PyprojectToml --> ShellScript
    
    classDef major-edit fill:#90EE90
    classDef minor-edit fill:#87CEEB  
    classDef context fill:#FFFFFF

Notes

• Architecture Change: This completely replaces the build system from dagger containerization to uv scripts - a significant architectural change that requires careful testing
• Environment Parity: The uv script approach should provide the same isolation benefits as the dagger container while being much simpler
• Dependency Versions: Preserved exact same datamodel-codegen version (0.26.3) to ensure identical pydantic v1 model generation
• CI Fix: This change specifically addresses the ModuleNotFoundError: No module named 'dagger' that was causing /poe build slash command failures

Session Info: Requested by AJ Steers (Aaron ("AJ") Steers (@aaronsteers)) - Session: https://app.devin.ai/sessions/5fc8aa08db104607acbe970add5f1002