[Docker] Use different `ROS_DOMAIN_ID`s for different containers

- [ ] When a docker container is created, generate a random number between 1 and 101 (inclusive).

Explanation: http://docs.ros.org.ros.informatik.uni-freiburg.de/en/foxy/Concepts/About-Domain-ID.html

- [ ] Also use only local network inside container with the variable `ROS_LOCALHOST_ONLY=1` (hopefully this will use only local network for it.

We should optimize even further:

- [ ] Use CycloneDDS instead of FastDDS per default
- [ ] Configure no multicast on CycloneDDS per default (use `.xml` configuration file)
- [ ] Use separate networking interface for docker that do not allow broadcasting into network but allow receiving data from it. (maybe ROS should be working on separate network, that would be a solution – see configuration file)

Start by locating the Docker container creation configuration and review how ROS environment variables and networking are currently set. Investigate the requested ROS_DOMAIN_ID and ROS_LOCALHOST_ONLY behavior, then assess the CycloneDDS XML and separate-networking proposals; done requires resolving the full checklist with a verified container setup.

Written by the indexing model from the issue text.