feat: Add configurable workflow status subscription for HTTP webhook publisher

[akhilpathivada]

Resolves #710

Summary

Enables configuration-based control over which workflow status changes trigger HTTP webhook events, matching the existing task status publishing behavior.

Problem

The HTTP webhook publisher (conductor.workflow-status-listener.type=workflow_publisher) currently hardcodes publishing only COMPLETED and TERMINATED workflow events, with no way to configure which statuses to receive. This is inconsistent with the task publisher which allows full configurability via subscribed-task-statuses.

Solution

Added subscribedWorkflowStatuses configuration property to enable selective workflow event publishing:

# New configuration property
conductor.status-notifier.notification.subscribed-workflow-statuses=RUNNING,COMPLETED,TERMINATED,PAUSED

# Valid values: RUNNING, COMPLETED, FAILED, TIMED_OUT, TERMINATED, PAUSED, RESUMED, RESTARTED, RETRIED, RERAN, FINALIZED

Changes

1. StatusNotifierNotificationProperties: Added subscribedWorkflowStatuses field with getters/setters
2. StatusChangePublisherConfiguration: Inject workflow status config and pass to publisher
3. StatusChangePublisher: Implement conditional checks in all 9 workflow lifecycle methods
4. StatusChangePublisherTest: Added comprehensive unit tests (17 test cases)
5. config.properties: Added configuration example with documentation

Testing

✅ All 9 workflow status methods tested with various configurations
✅ Null and empty list handling
✅ Build successful with no linter errors

[akhilpathivada]

@v1r3n @manan164 could you please help reviewing this?

[v1r3n]

Yes we are on it and should be part of next release if all looks good.