Forward zap fields to Sentry instead of dropping them

[biast12]

Description

ZapSentryAdapter was built on zapcore.RegisterHooks, whose callback receives a bare zapcore.Entry — a type that carries no fields. Every zap.String / zap.Uint64 / zap.Error attached to a log line was discarded before the event reached Sentry.

The result is that a production error arrives as a message, a caller and a stack, and nothing else: no guild id, no table name, no SQLSTATE. That is most of what you need to diagnose it, and it affects every service using this adapter.

Reimplemented as a real zapcore.Core that carries fields from both With() and the call site into Sentry Extra. When an error field is present it is folded into the exception value so the underlying error shows in the event title rather than the generic log message.

Check must add the wrapping core rather than the inner one, or zap writes straight through and Write never runs.

Type of Change

• Bug fix
• New feature
• Breaking change

Testing

Get an error that logs in sentry, you should see the zap fields now

Checklist

• My code follows the style of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works