Handle built-in protocol aliases

[RaimoNiskanen]

Fixes the bug discussed in:

https://erlangforums.com/t/how-to-get-recvtos-working-on-arch-linux/4654

[github-actions]

CT Test Results

    3 files    141 suites   49m 55s ⏱️
1 619 tests 1 563 ✅ 54 💤 2 ❌
2 340 runs  2 264 ✅ 74 💤 2 ❌

For more details on these failures, see this check.

Results for commit 0602b06.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot

[RaimoNiskanen]

I just pushed a suggestion to not use protocol name aliases for socket option names.

That would for example only allow {ip,recvtos} as the socket:setopts|getopts name for SOL_IP,IP_RECVTOS, and no longer allow {'IP',recvtos}, {hopopt,recvtos} and {'HOPOPT',recvtos}. The latter 3 stems from the protocols enumerated by getprotoent() (/etc/protocols) that have the same protocol number as SOL_IP.