Describe the feature or problem you’d like to solve

Hi 👋 , I checked the dependencies and noticed that it's a fairly short list of direct dependencies already 💪 .

But with the introduction of thelog/slog package in the Go standard library in Go 1.21 in 2023, there's a way to do structured logging without a third party dependency, so the number of direct dependencies could be reduced even further. As long as no specificlogrus features or conveniences are required, could it make sense to migrate toslog?

Proposed solution

Migrate from third party librarygithub.com/sirupsen/logrus to standard librarylog/slog.

Benefit: One less direct dependency (and thus lower supply chain risk, less maintenance burden for updates, maybe quicker build times)

Additional context

• Official blog post aboutlog/slog:https://go.dev/blog/slog
• Package reference:https://pkg.go.dev/log/slog