Fix: RPLidar angle blanking has no effect due to continue in nested loop

[letmehateu]

Overview

[Provide a brief overview of the changes in this pull request.]
(If applicable, linked issue: [ ])

Type of change

• Bug fix
• New feature
• Documentation improvement
• Bounty issue submission
• Other:

Changes

• Fix continue statement in rplidar_provider.py that targeted the inner for b in self.angles_blanked loop instead of the outer for angle, distance in data loop, causing blanked angle ranges to never be filtered out
• LiDAR readings from robot chassis/bracket reflections were always passed to the path planner as phantom obstacles

Checklist

• Code complies with style guidelines
• Self-review completed
• Documentation updated (if applicable)
• Local testing completed
• Tests added/updated (if applicable)

Impact

Any robot with non-empty angles_blanked config (Turtlebot4, test_lidar, etc.) was affected. Fixed reflections from the chassis were treated as real obstacles, potentially causing unnecessary stops or evasive manoeuvres.

FIxed: #2138

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[Wanbogang]

Hi @letmehateu
Can you make the test coverage according to codecov's suggestions?

[0xbyt4]

Tests pass on the buggy code too , test angles don't fall within blanked ranges after sensor_mounting_angle conversion. Please fix test data.

[letmehateu]

Tests pass on the buggy code too , test angles don't fall within blanked ranges after sensor_mounting_angle conversion. Please fix test data.

Thanks, should work properly now

[Wanbogang]

@letmehateu
please fix the conflict