chore(sdk): Log errors from EventLinkedChunk

[Hywan]

This patch logs errors from EventLinkedChunk and send them to Sentry (if Sentry is enabled).

The trick is to use #[instrument(err)] for logging errors. Quoting the documentation:

If the function returns a Result<T, E> and E implements
std::fmt::Display, adding err or err(Display) will emit error
events when the function returns Err:

#[instrument(err)]
fn my_function(arg: usize) -> Result<(), std::io::Error> {
    Ok(())
}

The level of the error value event defaults to ERROR.

It sounds exactly what we need.

---

• I've documented the public API Changes in the appropriate CHANGELOG.md files.
• This PR was made with the help of AI.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.96%. Comparing base (617c646) to head (619ded3).
⚠️ Report is 9 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6235      +/-   ##
==========================================
+ Coverage   89.94%   89.96%   +0.01%     
==========================================
  Files         370      370              
  Lines      101930   101917      -13     
  Branches   101930   101917      -13     
==========================================
  Hits        91685    91685              
+ Misses       6693     6687       -6     
+ Partials     3552     3545       -7     

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

[codspeed-hq]

Merging this PR will not alter performance

✅ 50 untouched benchmarks

---

_{Comparing Hywan:feat-sdk-event-cache-log-error-to-sentry (619ded3) with main (029148e)}

[stefanceriu]

That's a cool trick, did you check that it actually works? 😅