chore(autoware_launch): zero margin for outside the drivable area

[takayuki5168]

Description

Related PR: autowarefoundation/autoware.universe#4194
TODO after this PR is merged: Fix the issue of the outside drivable area wall appears much as expected.

This PR set the stop margin for outside the drivable area to zero.

Due to the issue of the outside drivable area wall tends to appear close to the other stop wall like crosswalk, intersection, etc, the several scenarios TIER IV is maintaining failed.

Tests performed

scenario simulator

Effects on system behavior

Almost nothing

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.

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.

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

[takayuki5168]

@ahmeddesokyebrahim
Due to the issue of optimization's result where the trajectory tends to be outside the drivable area around the stop point like crosswalk, intersection, etc, there was a degradation of the performance of Autoware after the PR autowarefoundation/autoware.universe#4194.

Is it okay to set the vehicle_stop_margin_outside_drivable_area to zero until the above issue will be resolved.

[ahmeddesokyebrahim]

Hi @takayuki5168 ,
I have approved the change. I just have a request if you may provide more information about this optimization result where the trajectory tends to be outside the drivable area . Thanks a lot!