[misc] split dependency preparation logic into individual dependency files for enhanced configuration flexibility

[mag1c-h]

Background

Currently, all dependency preparation logic is implemented in a unified public function. While this centralized approach simplifies the code structure, it introduces several limitations:

• Unable to set dependency-specific configuration items for each dependency
• Configuration interference between dependencies, making isolation difficult
• Violation of the Open/Closed Principle when adding new dependencies (requires modification of the common function)
• Inflexible dependency configuration for complex business scenarios

Solution

Split the dependency preparation logic into corresponding dependency files to achieve the following improvements:

Key Changes

• Remove the unified dependency preparation function
• Add independent preparation logic functions in each dependency file
• Provide separate configuration space for each dependency
• Maintain backward compatibility to ensure existing functionality remains unaffected

Implementation Details

1. Dependency Isolation: Each dependency has its own preparation function with non-interfering configuration items
2. Configuration Flexibility: Dependency-specific configurations can be set based on individual requirements
3. Easy Extension: New dependencies can be added without modifying other files
4. Maintenance Convenience: Dependency-related logic is centralized in respective files for easier maintenance

Impact Analysis

• Improved code maintainability and extensibility
• Enhanced dependency configuration flexibility
• Reduced coupling between dependencies