SocketWrapper: Refactoring Socket management

[leonardocavagnis]

No description provided.

[leonardocavagnis]

After investigation, the issue comes from the destructor in libraries/SocketWrapper/SocketWrapper.h:

~ZephyrSocketWrapper() {
    if (sock_fd != -1) {
         ::close(sock_fd);
    }
}

Removing these lines prevents the socket from being closed unexpectedly, and the Telnet session works as expected.
I’ve opened the PR with this change, but this is likely not the correct long-term fix.

Tagging @andreagilardoni to see if he can help point us toward the right approach.

[leonardocavagnis]

Please note that the code in this PR is fully functional and addresses issue #251. The encountered 'single connection' limitation does not stem from this library's logic, but from an incorrect Zephyr network configuration (see PR: #351).

cc @pennam

[github-actions]

Built 0.53.2-0.dev+3605386

CI run PASSED 🟢

Artifact	Board	Core	Tests	RAM	Sketches	Warnings	Errors
✅* zephyr_contrib	ek_ra8d1	📗	✅*	11.9%	2	2	-
	frdm_mcxn947	3 🏷️	✅*	58.0%	2	2	-
	frdm_rw612	1 🏷️	✅*	83.0%	2	2	-
✔️* zephyr_main	giga	4 🏷️	✅*	54.5%	44	14	-
	nano33ble	1 🏷️	✅*	78.7%	22	10	-
	nano_matter	📗	✔️*	⚠️ 85.7%	16	6	(2*)
	niclasense	2 🏷️	✅*	⚠️ 87.3%	20	10	-
	opta	4 🏷️	✔️*	46.7%	56	28	(2*)
	portentac33	3 🏷️	✔️*	⚠️ 95.1%	58	30	(8*)
	portentah7	3 🏷️	✔️*	47.3%	60	30	(2*)
✅* zephyr_unoq	unoq	📗	✅*	26.3%	52	10	-

Legend

Board	Test	Status description
🔥	🔥	Test run failed to complete.
❌	🔴	Test completed with unexpected errors.
✔️*	🚫	Test completed with errors, but all are known/expected.
✅*	🟡	Test completed with some warnings; no errors detected.
✅	🟢	Test passed successfully, with no warnings or errors.
🌑	🌑	Test was skipped.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}