fix(netlink): request unique port identifiers

[stephenlclarke]

Summary

Allow multiple Netlink route sockets in one process by requesting kernel-assigned port identifiers.

Binding every socket with nl_pid = getpid() makes the second concurrent socket collide with the first. Bind with port identifier zero, read the unique assigned identifier back with getsockname, and keep exposing it through the existing pid property.

The initialization path also closes the descriptor on every post-socket() failure and reports a dedicated socket-name error when the assigned address cannot be read or validated.

Testing

Added a Linux-only regression that opens eight concurrent route sockets and verifies every assigned port identifier is non-zero and distinct.

The installed macOS cross-compilation SDK is not compatible with the active Apple Swift compiler, so the Linux test is intentionally delegated to this pull request's native Linux CI rather than treated as locally executed evidence. git diff --check and focused Swift formatting of the added code pass.

Compatibility

The public property name remains pid for source compatibility, but its documentation now reflects Netlink semantics: it is a socket port identifier, not necessarily the process ID.

[crosbymichael]

I think we should use socklen_t throughout if you can.

[stephenlclarke]

Updated in d35cb51acce19b7df5ea5d0cf75e88e88a303331 and rebased onto current upstream. Both the bind buffer length and returned-address length comparison now use socklen_t; only the kernel netlink port identifier remains UInt32. The current ContainerizationNetlink production target cross-compiles successfully for aarch64 Linux/musl with Swift 6.3 and warnings as errors. This is compilation proof; I have not relabelled the earlier VM test failures as passes.