Fixed wasix network structure write in concordence to the read function

[ptitSeb]

Fixed wasix network structure write in concordence to the read function, and to wasix-libc.

Port is read as a "network endian" u16 but was wrote as a "big endian" u16, in practice reversing low/high byte of the u16.

[john-sharratt]

Need to run regression on this change as while its quite trivial it may not be backwards compatible with some of the compiled WASM. Lets test it with...

• rust native sockets
• rust with socket2
• C compiled sockets (e.g. curl )
• static-http-server

[theduke]

Ideally we'd have a C and a Rust snapshot tests for this.

One way to do it would be a simple tcp echo server.

But that will require a bit of time to write, I know.... not sure how urgent this is.

[ptitSeb]

There is a workaround in wasix-libc, so lowering the priority

[syrusakbary]

It seems we want to move this forward, but we need to test a bit more

[syrusakbary]

At the end we decided to stick with network byte ordering for WASIX (to keep it aligned with Linux). Closing the PR