docs: update the convention and mention sync-params workflow

[paulsohn]

Description

This updates and clarifies the current conventions:

• tier4_*_launch files are moved to autoware_launch, since Migrate tier4_xxx_launcher from autoware_universe into autoware_launch autoware#6774 .
• how the reusable nodes and example integration are (at least they should be) distinguished by autoware_universe / autoware_launch boundary
• the role differences of upstream (node) parameter files and downstream (launch) parameter files
  • the motivation why should the contributors update the node parameter files in autoware_universe, even though it is not directly used in the autoware_launch system
• how to use sync-params workflow to automate parameter file sync, which is introduced in Add sync-params workflow autoware#7048

Plus minor grammar fixes.

Disclaimer: the current version does not mention any ongoing migrations such as autoware index, and assuming that the autoware_universe is gigantic as it is for now. Can be updated after the migration gain its momentum.

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-804/
Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-804/contributing/coding-guidelines/ros-nodes/launch-files/
• https://autowarefoundation.github.io/autoware-documentation/pr-804/contributing/coding-guidelines/ros-nodes/parameters/

[technolojin]

There are some spoken English, but those are from the original.

For the sync-params process and its policy, I used the process and worked well.
Drawbacks are

• title is not intuitive (because of fixed template)
• parameter update could contain multiple updates of origins(universe, core), which makes hard to cherry-pick for specific combination.
• this sync-params process requires sequential process, so downtime occurs between the original update to this sync. manual process of merging could make almost zero downtime by merge two PRs in the same time.

[technolojin]

1. Instead of showing example and not explain detail, please describe what the modification is.

• topology modification
• replacement of using node
• add a new node, with parameter file registration

2. What "automatically" load the newly added package means?

[technolojin]

It seems the sentences are from the original. Is someone have any idea of this?

[sasakisasaki]

Thank you for your comment. Personally, I guess we can remove the second sentence as this my proposal. Because what we want to say here is, "please fix launch file if you want to launch new package which is added to latest autoware_universe".

[xmfcx]

A few editorial fixes from a close read. The first three are content defects (a truncated sentence, a fragment, and a verb that inverts an instruction's meaning); the rest are minor. Left as committable suggestions where possible.

Non-inline note: the mermaid diagram still shows pose_estimator.launch.xml (line 43) while the updated prose now uses pose_twist_estimator — worth aligning for consistency, though it's a pre-existing node outside this diff.

[paulsohn]

@xmfcx Thanks for the review! I have updated the sentences as in 6bbf6f1 . Marking all of your comments as resolved.

[sasakisasaki]

Reviewed. I agree with merging this PR while put some quick win comments 👍

[sasakisasaki]

@xmfcx @mitsudome-r Could you please review this PR?