feat(x1): update livox min range to 1.0m

[yn-mrse]

Description

!!! This PR assumes that the #104 has been merged. !!!

This PR applies to the close-range version of livox_horizon.
With this PR, the vehicle will be able to see up to a close distance of 1.0[m], which is the limit of the hardware specs of the close range version of livox.

Related links

T4PB-25423 (TIERIV, INC. INTERNAL LINK)
#104

Tests performed

Assumptions:
Originally, the min_range crop function was used to remove near-field noise from lidar sensors.
In the case of the livox sensor, there is a feature that sensor noise is detected in front of the actual object.
Especially when driving on a narrow road, sensor noise from obstacles on the left and right of the lane may enter the lane.
In this case, the vehicle may erroneously detect as if there is an obstacle ahead.

Validation:
A running test was conducted on a narrow road with a width of 1.75 [m], which is the worst condition assumed under x1 usage conditions.
We have confirmed that it can pass through obstacles without false detection.

Verification:
After launch, confirm that the settings have been reflected with the following command.
ros2 param get /sensing/lidar/front_center/crop_box_filter_min_range max_x
As expected, the result is shown below.
Double value is: 1.0
I did the same test on the left and right and got the same results.

Notes for reviewers

This PR assumes that the #104 has been merged.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.
• The PR has been properly tested.
• The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.
• The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

[tier4-autoware-public-bot]

The backport to beta/v2022.05.1 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-beta/v2022.05.1 beta/v2022.05.1
# Navigate to the new working tree
cd .worktrees/backport-beta/v2022.05.1
# Create a new branch
git switch --create backport-107-to-beta/v2022.05.1
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 d5deb74b39ba3a4e595e13e6fc8a6d0cc95718e4
# Push it to GitHub
git push --set-upstream origin backport-107-to-beta/v2022.05.1
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-beta/v2022.05.1

Then, create a pull request where the base branch is beta/v2022.05.1 and the compare/head branch is backport-107-to-beta/v2022.05.1.