Extended LIDAR functionality

[simoooong]

Description

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes # (Extend LIDAR to have 360 input every frame #858)

I have updated the lidar_distance node to buffer the latest pointcloud data to be reused in the next frame.
LIDAR will now perceive the new and old data (last frame) to have a 360 degree perception.

Type of change

• New feature (non-breaking change which adds functionality)

Does this PR introduce a breaking change?

• No

Most important changes

See changes

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• [-] I have commented my code, particularly in hard-to-understand areas
• [-] I have made corresponding changes to the documentation
• [-] My changes generate no new warnings
• [-] I have added tests that prove my fix is effective or that my feature works (might be obsolete with CI later on)
• [-] New and existing unit tests pass locally with my changes (might be obsolete with CI later on)

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch 858-feature-extend-lidar-to-have-360-input-every-frame

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}