feat(behavior path): select excutable behavior

[taikitanaka3]

Related Issue(required)

Description(required)

launch selected behavior for behavior path planner using "empty module" registering to behavior tree

Otherways
Iets's say we can add conditions not executable for each module like 18a902b however in this condition it's extraordinary to run module every time it's update even though module construction is unnecessary.

Issues
Behavior path planner couldn't select executable modules from ros args.

Solution
In behavior tree cpp behavior tree is created at first with defined xml and it's difficult to change behavior tree architecture form considering ros parameters or launch arg. So in this PR behavior module is registered as empty module while keeping module roles with empty.

Note : lane following module is always enabled by default and no choice of disable option for now.

Review Procedure(required)

Task Assigned by @TakaHoribe
cc: @rej55

launch psim

lane change enabled

lane change disabled

set parameter in ArchitectureProposal_launcher

    enable_lane_change: fal;se
    enable_side_sift: true
    enable_avoidance: true
    enable_pull_over: true
    enable_pull_out: true

Related PR(optional)

Pre-Review Checklist for the PR Author

PR Author should check the checkboxes below when creating the PR.

• Read commit-guidelines
• Assign PR to reviewer

If you are adding new package following items are required:

• Documentation with description of the package is available
• A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer

Reviewers should check the checkboxes below before approval.

• Commits are properly organized and messages are according to the guideline
• PR title describes the changes

Post-Review Checklist for the PR Author

PR Author should check the checkboxes below before merging.

• All open points are addressed and tracked via issues or tickets

CI Checks

• Build and test for PR / build-and-test-pr: Required to pass before the merge.
• Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
• Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

[stale]

This pull request has been automatically marked as stale because it has not had recent activity.

[kenji-miyake]

@taikitanaka3 Please resubmit this to main if you still need this PR. 🙏