feat: update acceleration limit

[brkay54]

Description

Following the recent discussions in the ODD Working Group, we've agreed to set the deceleration limit to 0.255G (~2.499 m/s²) for Dense Urban ODD. To implement this change, we need to update the acceleration limit parameters on both the planning and control sides.

For more details, refer to the ODD WG Discussion page: ODD WG Discussion #5290

Tests performed

I tested Dense Urban ODD scenarios in the local.

Not applicable.

Effects on system behavior

Not applicable.

Interface changes

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.

[yuki-takagi-66]

I feel that this PR is too specific to Dense Urban ODD. Can I ask you to reconsider?

[yuki-takagi-66]

This change may be only for Dense Urban ODD.

[yuki-takagi-66]

stopped_acc does not denote deceleration value, but denotes pedal position after the stop has achieved.
Hence this change is not required.

[yuki-takagi-66]

In order to follow the trajectory planned with limit.min_acc and limit.max_acc in the planning params, this values must be greater than planning params. Because we need a margin for disturbance and error.
However, I think we have an option to align these values to the limit.min_acc and limit.max_acc in common.pram.yaml to restrict the feedback control.

[xmfcx]

@Igata-ctrl @mitsudome-r what should be done about this PR?

@brkay54 won't be able to work on this task anymore. But how should we handle scenarios and parameters like these?

Are there other scenarios that the public cannot access? I think the autoware_launch default parameters should be tuned for scenarios that are accessible by the public.