Fix: Correct argument order for workflow import subject and description templates

[ashu82492]

Issue

When importing workflows, the subjectIdTemplate and descriptionTemplate arguments were being passed in the wrong order to the workflow builder, causing these templates to be swapped during the import process.

Changes Made

Fixed argument order in WorkflowManager.java

• Swapped the order of descriptionTemplate and subjectIdTemplate parameters

Fixed return value in import logic [Please review if this is correct]

• Corrected the return statement to return the properly configured workflow object instead of inWorkflow
• This ensures the workflow returned includes all the updates from the import operation

Removed unused import

• Removed unused com.google.common.collect.Sets import

Added test assertions

• Subject ID and Description templates are correctly set to "Subject"
• Tests cover both initial import and idempotent import scenarios

Updated test fixture

• Added descriptionTemplate and subjectIdTemplate fields to workflow_details.json fixture to properly test the scenario

Testing

All existing tests pass and tested the import feature locally.

[ashu82492]

Please double verify if this is correct.
This should return the the updated workflow rather than input inWorkflow.

[tusharmndr]

ImportResult should be newly imported workflow, but here workflow might be incomplete as the Dto workflow object might not have complete transition and states,
Please re-read the workflow for import result, example schema

.flatMap(schemaSummary -> schemaStore.read(schemaSummary.getId()))
                .map(schema -> new ImportResult<>(schema, true, null))