Bug: Wrong mapping of the zmq ports

[johnnyasantoss]

Describe the bug
The zmq ports get mapped incorrectly, and the UI also shows the wrong values.

hashblock zmq launched internally on port 28336

28334 (rawblock stream) gets mapped as external 28335 (OrbStack UI)

Polar UI shows external port 28335 (prev mapped to rawblock) as the one for hashblock notification

To Reproduce
Steps to reproduce the behavior:

1. Create a new network with a bitcoind instance
2. Open the docker logs
3. Search for Command-line arg: zmqpubhashblock (hit enter to actually filter) - take note of the port
4. See the docker desktop or similar ui/cli to see the mapping being done
5. See connect tab on the bitcoin node on the Polar UI (see the wrong port being exposed)

Expected behavior
Export the correct port and add another item to the connect tab to correctly identify rawblock/hashblock streams

Desktop (please complete the following information):

• OS: MacOS Sonoma Version 14.7 (23H124)
• Polar Version: 3.0.0
• Docker Version: 27.1.2
• Docker Compose Version: 2.29.2

Additional context
The stream I need is the hashblock but there's no simple way to expose that