Improved Port Checking for Prysm and Execution Client

Description

This PR enhances the port checking functionality in the node checker to better handle Prysm's specific port requirements and improve UDP port visibility. The changes ensure proper detection and reporting of all necessary ports for both consensus and execution clients.

Changes

• Added separate checks for Prysm's specific ports (12000 UDP and 13000 TCP)
• Implemented consistent checking of execution client port 30303 (TCP/UDP) regardless of consensus client
• Improved UDP port visibility in the listening ports overview
• Updated port checker to handle both TCP and UDP ports separately
• Enhanced output messages for better clarity and consistency

Testing

The changes have been tested with:

• Prysm consensus client (ports 12000 UDP and 13000 TCP)
• Geth execution client (port 30303 TCP/UDP)
• Other consensus clients (port 9000 TCP)

Impact

These changes ensure that:

1. All necessary ports are properly checked and reported
2. UDP ports are correctly detected and displayed
3. Port checking is consistent across different client combinations
4. Output messages clearly indicate which ports are being checked

Related Issues

• Fixes port visibility issues for UDP ports
• Resolves inconsistent port checking for Prysm
• Ensures execution client port is always checked