Feature/robot status bridge

[SeanChangX]

These changes collectively enhance the functionality and maintainability of the robot_status_bridge application, providing a robust setup for ROS environments and enabling comprehensive battery monitoring.
This pull request introduces several significant updates to the robot_status_bridge application, focusing on setting up the ROS environment, configuring Docker, and implementing new ROS nodes for monitoring robot status and battery levels.

ROS Environment Setup:

• Added a function source_ros_environment in .bashrc to set up the ROS environment for different distributions (humble and noetic). This includes sourcing the necessary setup files and setting up custom aliases.

Docker Configuration:

• Created a Dockerfile with multiple stages for setting up the base image, creating a non-root user, installing development tools, and setting the entrypoint.
• Added a docker-compose.yaml file to define the voice_nav service, including build context, environment variables, volumes, and entrypoint configuration.
• Introduced an .env file to set environment variables like ROS_DISTRO and COMPOSE_BAKE.

ROS Nodes Implementation:

• Implemented a battery_monitor package with CMake and package configuration files, and created battery_publisher and battery_subscriber nodes to monitor and publish battery status. [1] [2] [3] [4]
• Developed a robot_status_monitor package with message definitions and nodes to publish and subscribe to robot status, including various system metrics like CPU usage, RAM usage, and Wi-Fi signal strength. [1] [2] [3] [4] [5]

Entrypoint Script:

• Added an entrypoint.sh script to source the ROS workspace and run the robot_status_node.