feat(mq): add RocksMQ input/output stub (config + protocol placeholder)

[luoluoyuyu]

Note

Low Risk
Primarily additive changes gated behind a new config type; existing Kafka paths are untouched, but selecting rocksmq will currently drop/ignore messages due to stubbed poll/send behavior.

Overview
Adds a new rocksmq input/output type to task configuration and wiring, so YAML can specify InputConfig::RocksMQ / OutputConfig::RocksMQ and providers construct corresponding runners.

Introduces placeholder RocksMQ protocol modules and config structs for input and output; the implementations are explicitly stubs (poll() always returns Ok(None), send() is a no-op) intended to be replaced once a real RocksMQ client is available.

^{Written by Cursor Bugbot for commit e8bb938. This will update automatically on new commits. Configure here.}

[luoluoyuyu]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

[cursor]

Serde tag and input_type/output_type value mismatch

High Severity

The RocksMQ variant on an enum with #[serde(rename_all = "kebab-case")] produces a serde tag value like "rocks-m-q" (serde inserts a hyphen before each uppercase letter). But input_type() returns "rocksmq" and output_type() returns "rocksmq". The validation in InputGroup::from_yaml_value and WasmTaskConfig::from_yaml_value compares the raw YAML tag against these method return values, so it will always fail with a type mismatch error for RocksMQ configs. Either add #[serde(rename = "rocksmq")] to the RocksMQ variants, or change the return values of input_type() and output_type() to match the serde-generated tag.

Additional Locations (1)

• src/runtime/task/processor_config.rs#L571-L572