[BUG]: Server endpoint bind failure & inconsistent IPv4 TCP/UDP endpoint advertisement

### vSomeip Version

v3.1.20.3

### Boost Version

1.71.0

### Environment

Ubuntu 20.04.6

### Describe the bug

We are encountering an intermittent issue while creating server endpoints and advertising SOME/IP Service Discovery entries.

At runtime, the server endpoint creation occasionally fails with the following error:

create_server_endpoint Server endpoint creation failed.
Reason: acceptor bind: Address already in use
Port: 50002 (reliable=reliable)

This suggests the TCP endpoint bind on port 50002 is failing because the address/port is already occupied.

### Reproduction Steps

_No response_

### Expected behaviour

For IPv4 communication, we expect the SD Offer to advertise both UDP and TCP endpoints for the same service instance, for example:

UDP endpoint → 192.168.10.16:50002

TCP endpoint → 192.168.10.16:50002

Both should appear in the IPv4 Endpoint Options Array within the same SD Offer.

### Logs and Screenshots

In packet captures, we see inconsistent endpoint advertisement.

Case 1 – Both UDP + TCP endpoints present (Expected)
IPv4 Endpoint Option (192.168.10.16:50002 (UDP))
Protocol: 17 (UDP)
Port: 50002

IPv4 Endpoint Option (192.168.10.16:50002 (TCP))
Protocol: 6 (TCP)
Port: 50002
Case 2 – Only TCP endpoint present
IPv4 Endpoint Option (192.168.10.15:50002 (TCP))
Protocol: 6 (TCP)
Port: 50002

In this case, the UDP endpoint is missing from the SD Offer.

We have also observed scenarios where only UDP is advertised.