Silent failure when unable to bind port

[KenanHH]

When the application attempts to bind to a port that is already in use or otherwise unavailable, it exits without reporting any error. The application terminates with a regular status code instead of providing feedback about the failure to bind the port.

Steps to Reproduce:

• Start an instance of the application binding to a specific port (e.g., 8080).
• Attempt to start another instance of the application that tries to bind to the same port.
• Observe that the second instance exits silently without any error message or indication of the failure.

Expected Behavior:

The application should provide an error message indicating that it could not bind to the specified port and should exit with a non-zero status code.

Actual Behavior:

The application exits silently with a regular status code, providing no indication of the failure to bind the port.

[22:55] ubuntu@kenan-remote ~/Projects/FastEdge-lib  ./target/release/cli http --port 80 --wasm /home/ubuntu/Projects/FastEdgeApps/rust/target/wasm32-wasi/release/jwt_token_validate.wasm --envs jwt-sign-secret=kenan-testing

[22:55] ubuntu@kenan-remote ~/Projects/FastEdge-lib $ echo $?
0