Micro Ros Agent if not configured properly or left with default value, code execution will stop without much debug info.

Nobody has claimed this yet.

- Hardware description: Doit ESP32 Dev Kit
- RTOS: Simple publisher int32 example.
- Installation type: micro_ros_setup
- Version or commit hash: jazzy

#### Steps to reproduce the issue

- Clone this repo.
- Source the terminal using export.sh and then go to the Int32_publisher example.
- Do idf.py build flash monitor.(Make sure esp32 is connected while doing so).
- I delibrately left the idf.py menuconfig step.
- Once, flashed, you'll see notice that program gets aborted indicating the line at which issue occured without additional info.

#### Expected behavior
The program should atleast output the default config such as ssid, password, micro-ros-agent config. Giving more context and ensuring network is intialized properly and any issue with configuration could be easily debugged.

#### Actual behavior
The program stops indicating the line where issue occured.

#### Proposed Changes:
Adding network intialization check and logging default configuration in the code.

Start by reproducing the issue in the Int32_publisher example with `idf.py build flash monitor` after skipping menuconfig. Inspect the abort path and the network and micro-ROS agent configuration handling. Done means the example reports its configuration context and clearly identifies network initialization or configuration failures instead of stopping with only a line reference.

Written by the indexing model from the issue text.