refactor(mission_planner)!: add autoware prefix and namespace

[kosuke55]

Description

Part of:

• Prefix packages with autoware_ prefix and keep code in autoware namespace autoware#4569

Tests performed

psim

~/pilot-auto (main %=)
$ ros2 launch autoware_static_centerline_generator run_planning_server.launch.xml vehicle_model:=lexus
[INFO] [launch]: All log files can be found below /home/kosuke55/.ros/log/2024-06-10-19-12-14-782525-DPC2103006-787757
[INFO] [launch]: Default logging verbosity is set to INFO
[WARNING] [launch_ros.actions.node]: Parameter file path is not a file: /home/kosuke55/pilot-auto/install/autoware_launch/share/autoware_launch/config/planning/scenario_planning/lane_driving/motion_planning/path_optimizer/path_optimizer.param.yaml
[INFO] [vector_map_tf_generator-1]: process started with pid [787760]
[INFO] [lanelet2_map_visualization-2]: process started with pid [787762]
[INFO] [main-3]: process started with pid [787764]
[INFO] [rviz2-4]: process started with pid [787766]
[INFO] [app.py-5]: process started with pid [787768]
[app.py-5]  * Serving Flask app 'app'
[app.py-5]  * Debug mode: on
[app.py-5] WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
[app.py-5]  * Running on http://localhost:4010/
[app.py-5] Press CTRL+C to quit
[app.py-5]  * Restarting with stat
[app.py-5]  * Debugger is active!
[app.py-5]  * Debugger PIN: 474-966-708
[rviz2-4] [INFO 1718014336.062522836] [rviz2]: Stereo is NOT SUPPORTED (operator()() at ./src/main.cpp:62)
[rviz2-4] [INFO 1718014336.062638393] [rviz2]: OpenGl version: 4.6 (GLSL 4.6) (operator()() at ./src/main.cpp:62)
[rviz2-4] [INFO 1718014336.202570913] [rviz2]: Stereo is NOT SUPPORTED (operator()() at ./src/main.cpp:62)

Effects on system behavior

change only package name no change on topic name

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.