Add LiDAR IP configuration example for Pulsar SL450/ME450 devices

[matthewwachter]

Summary

• Adds new example 4.lidar_ip_config for configuring network settings (IP address and subnet mask) on LiDAR devices
• Uses the LiDAR vendor protocol instead of GVCP ForceIP, which LiDAR devices don't support

Why this is needed

The existing 2.device.forceip example uses GVCP (GigE Vision Control Protocol), which only works with GigE Vision cameras like Gemini 335Le/435Le. LiDAR devices (SL450, ME450, MS600) use mDNS for discovery and a proprietary vendor protocol for configuration, so they ignore GVCP ForceIP commands. The LiDARHostCompute project only allows changing IP address and not Subnet.

Changes

• examples/lidar_examples/4.lidar_ip_config/lidar_ip_config.cpp - Main tool
• examples/lidar_examples/4.lidar_ip_config/CMakeLists.txt - Build config
• examples/lidar_examples/4.lidar_ip_config/README.md - Documentation

Note

Gateway configuration is not included because the LiDAR firmware protocol does not support it (no OPCODE_SET_GATEWAY exists in LiDARProtocol.hpp).