fix(log_bridge): start with the default config

[mfaferek93]

The shipped config/log_bridge.yaml sets exclude_nodes: [] and include_only_nodes: []. Empty YAML lists are untyped, so launching the node with this file aborts at startup:

terminate called after throwing an instance of 'rclcpp::exceptions::InvalidParameterValueException'
  what():  parameter_value_from failed for parameter 'exclude_nodes': No parameter value set
[ros2run]: Aborted

The node code is correct (declare_parameter<std::vector<std::string>>(..., {})); only the shipped YAML breaks it. This comments out the two lines with non-empty examples, so the node's typed defaults apply.

Before: ros2 run ros2_medkit_log_bridge log_bridge_node --ros-args --params-file config/log_bridge.yaml -> Aborted.
After: LogBridge started (topic=/rosout, severity_floor=30, prefix=LOG).

Closes #444

[Copilot]

Pull request overview

Fixes ros2_medkit_log_bridge startup failure when using the shipped default params file by avoiding untyped empty YAML lists for exclude_nodes / include_only_nodes, allowing the node’s typed declared defaults to apply.

Changes:

• Remove exclude_nodes: [] and include_only_nodes: [] from config/log_bridge.yaml.
• Add commented guidance/examples for enabling those filters with non-empty lists.

[bburda]

Verified the fix. The two list params are the only empty-list entries in the YAML, the node declares both with typed empty-vector defaults, so commenting them out keeps the same behavior and stops the startup abort. No other empty lists remain.

Dismissing to complete a deeper review before sign-off.

[bburda]

Verified the fix across the config, the node parameter declarations, the launch path and other params files in the repo. The two commented-out list params are the only empty-list entries, the node declares both with typed empty-vector defaults so behavior is unchanged, no launch file or other params file re-introduces the empty list, and the installed config is the edited one. Startup abort is resolved.