Socket API needs method to control source port for TCP client

[jphickey]

Is your feature request related to a problem? Please describe.
The bind() call could be used on a client-side role (without listen()) to control the source port for outgoing TCP connections.

The OS_SocketBind() API assumes a server-side role, in that it does both a bind() and listen() call underneath.

Currently, the OSAL API does not have any way to control the port used for a TCP connection on the client side.

Describe the solution you'd like
Introduce a method that can be used to control the source port used for client-side connections

For example: OS_SocketBindClient() and OS_SocketBindServer() (retaining existing OS_SocketBind for compatibility)

Describe alternatives you've considered
This could potentially be done in OS_SocketConnect, such as OS_SocketConnectWithSourcePort() ... but keeping it in bind keeps it more closely related to standard sockets API.

Additional context
This must be done with only new functions, cannot change definition of current OS_SocketBind.

Requester Info
Joseph Hickey, Vantage Systems, Inc.