[feature] Support version creation triggered by workflow

[YoungerYang-Y]

Is your feature request related to a problem? Please describe.
In the current Zadig platform, after testers complete version testing, they need to manually create a new version from the version management menu to release it. This approach has the following issues:

1. Process fragmentation: Version creation is completely disconnected from workflows, preventing the formation of a complete DevOps pipeline
2. Excessive manual intervention: Requires manual operations by testers, increasing the possibility of errors
3. Low efficiency: Unable to achieve automated release processes
4. Difficult traceability: The relationship between versions and workflows is unclear, making it difficult to trace version sources

This situation prevents the realization of true automated DevOps processes, especially in agile development scenarios that require frequent version releases.

Describe the feature you'd like
We hope to add a new task type in workflow tasks: "Create Version" task. This task should have the following characteristics:

1. Trigger method: Support automatic version creation during workflow execution
2. Data source: Able to generate version information based on workflow variables, outputs from preceding tasks, or other workflow context information
3. Version information configuration:
   • Version name (supports variable interpolation)
   • Version description
   • Associated products and services
   • Version tags and metadata
4. Integration capability: Created versions should be associated with the current workflow for easy traceability and auditing
5. Conditional control: Support conditional judgment, only create versions when specific conditions are met

Through this feature, we can achieve:

• Automatic creation of test versions upon test completion
• Automatic creation of release versions upon successful build
• Automatic creation of corresponding versions based on branches or tags

Describe alternatives you've considered
We have currently tried the following alternative solutions, but none can completely solve the problem:

1. Generic image distribution task: Can push images to image repositories, but cannot create corresponding version records in Zadig's version management
2. API call task: Although version management API can be called through HTTP requests, it requires additional configuration and maintenance costs
3. Script task: Can be implemented through custom scripts, but lacks unified management interface and error handling mechanisms

In comparison, the built-in "Create Version" task will be more stable, user-friendly, and better integrated into workflows.

Additional context

• Scope of impact: This feature mainly affects workflow execution and version management modules
• Compatibility: Need to ensure full compatibility with existing version management functionality
• Security considerations: Should consider access control to ensure only authorized workflows can create versions
• Version information: Current Zadig version v4.1.0
• Priority: High - This is a key feature for implementing complete DevOps pipelines