[Feature Request]: Wait for websocket message

### What would you like to happen?

Migration: https://issues.apache.org/jira/browse/HOP-4099

It would be super useful to be able to connect with a web socket and wait for a (certain) message.

Use case:

Starting an asynchronous method via a REST Call, that one gives me the url to a web socket and notifies me via that web socket that it is done.

Useful options:

Max time-out
Send heart-beats (with configurable time between)
Only react on a message that meets a filter (This probably is a lot of work, could be a possible follow-up story). Use case: some kind of event bus
I like the artemis selector a lot for filtering

https://github.com/apache/activemq-artemis/tree/main/artemis-selector/src/main/java/org/apache/activemq/artemis/selector/filter
https://activemq.apache.org/components/artemis/documentation/latest/filter-expressions.html
https://search.maven.org/artifact/org.apache.activemq/artemis-selector/2.24.0/jar
https://search.maven.org/artifact/org.apache.activemq.examples.jms/artemis-static-selector-example/1.0.0/jar
Example: https://timjansen.github.io/jarfiller/guide/jms/selectors.xhtml

### Issue Priority

Priority: 3

### Issue Component

Component: Workflows

Start with the linked migration issue HOP-4099 and the Apache Artemis selector references in the report. Clarify the workflow entry point and scope for websocket waiting, including timeout and heartbeat behavior, while treating message filtering as a possible follow-up. Done should mean an agreed, testable feature definition covering the required options.

Written by the indexing model from the issue text.