bug(besu-AIO): Cannot communicate with Besu when using Docker networks

[LordKubaya]

Describe the bug

When deploying a Hyperledger Cactus Besu AIO environment using Docker, the Besu server is configured to listen on 127.0.0.1.
This causes communication failures because other containers cannot access services bound to localhost inside another container.
The expected configuration should bind Besu to 0.0.0.0 so that it becomes reachable within the Docker network.

---

To Reproduce

Steps to reproduce the behavior on a successfully deployed Hyperledger Cactus cluster:

1. Deploy the Besu AIO container using Docker Compose or similar.
2. Attempt to connect to the Besu RPC endpoint from another container.
3. Requests fail because Besu is only listening on 127.0.0.1.

---

Expected behavior

Besu should bind to 0.0.0.0 so that RPC and WebSocket endpoints are accessible to other containers in the same Docker network.
This would allow plugins, connectors, and validators to communicate with Besu normally.