Implement read/write timeouts for BIO datagram

[smittals2]

Issues:

CryptoAlg-3287
CryptoAlg-3331

Description of changes:

Added

• BIO_CTRL_DGRAM_SET_RECV_TIMEOUT
• BIO_CTRL_DGRAM_GET_RECV_TIMEOUT
• BIO_CTRL_DGRAM_SET_SEND_TIMEOUT
• BIO_CTRL_DGRAM_GET_SEND_TIMEOUT

Testing:

• Read timeout test added
• For Write timeout, the APIs are tested but the behavior is not. Filling the send buffer to force a timeout with UDP is unreliable across different OS (buffers can be very large, or instead of timing out OS starts dropping packets).

Callouts:

• We also change how we track error states for datagram sockets. Previously, on read/write errors, we would only store certain errors if they were considered "retryable" or non-fatal. In the case of timeouts, WSAETIMEDOUT on Windows is not considered retriable and therefore was never tracked in our error handling, making that code path unreachable. This PR changes this behavior to store the error value regardless of whether it is retriable, so we can always track the error state.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.

[github-actions]

clang-tidy made some suggestions

[codecov-commenter]

Codecov Report

❌ Patch coverage is 78.20513% with 17 lines in your changes missing coverage. Please review.
✅ Project coverage is 78.71%. Comparing base (d6a3724) to head (743ef6b).
⚠️ Report is 41 commits behind head on main.

Files with missing lines	Patch %	Lines
crypto/bio/dgram.c	76.56%	15 Missing ⚠️
crypto/bio/bio_socket_test.cc	85.71%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2610      +/-   ##
==========================================
- Coverage   78.72%   78.71%   -0.02%     
==========================================
  Files         645      645              
  Lines      110641   111156     +515     
  Branches    15646    15701      +55     
==========================================
+ Hits        87103    87494     +391     
- Misses      22840    22970     +130     
+ Partials      698      692       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[justsmth]

Missing part 2?

[smittals2]

Its intentionally not there, i wasn't able to simulate forcing a write timeout. I'll get rid of the pt. 2 from the comments. In SocketDatagramTimeouts (the test above this one) we just do a simple get/set check to ensure API works correctly. But we are not able to test the behavior.