SSL_reset_early_data_reject does not clear out unreported bytes written

### Problem:

SSL_reset_early_data_reject does not clear out unreported bytes written. As a result, after early data is rejected and SSL_reset_early_data_rejected() is called, SSL_write most likely fail with BAD_LENGTH because of false length check.

### Solution:

Port boringssl fix https://boringssl.googlesource.com/boringssl/+/b01c5055d9efc6b114d5395ac1cc0080d9941a09

Start at the SSL_reset_early_data_reject and SSL_reset_early_data_rejected entry points, then compare their behavior with the referenced BoringSSL commit. Verify the early-data rejection state and unreported bytes handling, and confirm that a subsequent SSL_write no longer fails with BAD_LENGTH.

Written by the indexing model from the issue text.