[DEFECT] Manual deploy workflow (cicd_8-manual-deploy.yml) fails with invalid input parameters

Problem Statement

The newly created manual deploy workflow (cicd_8-manual-deploy.yml) intended to replace legacy-release_publish-dotcms-docker-image.yml is not functioning correctly. The workflow has multiple issues:

1. Validation errors - The workflow fails on startup with parameter errors
2. Confusing input options - Some duplication exists in the workflow inputs
3. Missing clarity - Branch or tag selection and extension parameter usage is unclear

Error Message:

Invalid workflow file: .github/workflows/cicd_8-manual-deploy.yml#L121
The workflow is not valid. 
- .github/workflows/cicd_8-manual-deploy.yml (Line: 121, Col: 11): Input change-detection is required, but not provided while calling.
- .github/workflows/cicd_8-manual-deploy.yml (Line: 123, Col: 25): Invalid input, validation-level is not defined in the referenced workflow.

Impact: Unable to manually deploy Docker images using the new workflow, blocking the deprecation of the legacy workflow.

Steps to Reproduce

1. Navigate to Actions tab in dotCMS/core repository
2. Select the cicd_8-manual-deploy workflow
3. Click "Run workflow"
4. Fill in the required parameters
5. Click "Run workflow" button
6. Observe startup failure with validation errors

Acceptance Criteria

• Fix the change-detection input - either provide required input or make it optional in the called workflow
• Remove the invalid validation-level input reference (not defined in referenced workflow)
• Simplify and deduplicate input options for clarity
• Ensure branch/tag selection works as expected
• Add clear documentation for the extension parameter
• Verify the workflow runs successfully end-to-end
• Document the migration path from legacy workflow

dotCMS Version

GitHub Actions workflow - main branch (commit c30b53f)

Severity

High - Major functionality broken

Links

• NA (internal engineering issue)

Start with .github/workflows/cicd_8-manual-deploy.yml, especially the reported errors near lines 121 and 123, and compare it with the referenced legacy workflow. Trace the called workflow's inputs and review the acceptance criteria for branch/tag selection, extension documentation, and migration notes. Verify completion by running the manual deployment workflow end-to-end.